# New Device Setup Guide

This guide explains how to get your full Monorepo, AI Orchestrator, CLI agents, and Knowledge Base (`ctx-guard`) up and running on a brand new device.

## Prerequisites

Ensure the following tools are installed on your new device:
- `git`
- `python3.12` or newer
- `pipx`
- `curl`

## Step 1: Clone the Monorepo

Clone the Orchestrator to your preferred workspace directory (e.g., `~/coden`):
```bash
mkdir -p ~/coden
cd ~/coden
git clone https://git.d-hive.de/ankn/Orchestrator.git
cd Orchestrator
```

## Step 2: Set up the Knowledge CLI (`ctx-guard`)

The `ctx-guard` tool requires a Python virtual environment.

```bash
cd ~/coden/Orchestrator
python3 -m venv .venv
source .venv/bin/activate

# Install the monorepo-cli package in editable mode
cd shared/tools/monorepo-cli
pip install -e .
```

To register the new machine to your federation topology, run the built-in onboard command:
```bash
# Replace <machine_name> with your device name
ctx-guard onboard <machine_name> "privat,dhive,bahn,shared"
```

## Step 3: Install the AI CLIs

Install the Codex CLI:
```bash
curl -fsSL https://chatgpt.com/codex/install.sh | sh
```

Install the Antigravity CLI:
```bash
curl -fsSL https://antigravity.google/cli/install.sh | bash
```

Run `codex login` and `agy login` in your terminal to authenticate via the browser.

## Step 4: AI Agent Customizations

Because the `.agents` folder is now version-controlled inside the Orchestrator monorepo (`~/coden/Orchestrator/.agents`), your AI agents will *automatically* discover your custom skills (like `model_advisor`) and rules (like strictly using `ctx-guard` for knowledge tasks).

To ensure your models catalog is kept up to date, you can manually run the updater script:
```bash
cd ~/coden/Orchestrator
./.agents/scripts/update_models_config.sh
```

*(Note: In your primary environment, an agent has scheduled this as a daily cron job. You can instruct the agent to set up the same schedule on the new device by typing `/schedule daily run .agents/scripts/update_models_config.sh` in the chat).*

## Step 5: Sync Federation Repositories

Finally, pull down the rest of your private and shared federation repositories from the `dhive` GitLab:
```bash
ctx-guard fed-sync --context dhive
```

Your environment is now fully identical to your original machine!