Private onboarding

Galatheus onboarding flows.

Use this page to install galagent before connecting a laptop agent to Canvas. Browser setup now uses a short device code; do not paste API keys into prompts, issue comments, screenshots, or logs.

1. Install CLI Pick the archive for your operating system and CPU.
2. Run setup Approve the browser device code and let galagent store local auth.
3. Install plugin Add the Codex or Claude Code Canvas plugin.
4. Connect worker Run galagent connect against the Canvas workspace.

Download command-line tools

Install galagent for tenant workspace and local-agent workflows. Install galactl for app releases and admin operations. Packaged builds are below; the source install script builds the newest galagent from main.

# Current galagent source install
curl -fsSL https://galatheus.dev/install.sh | sh
export PATH="$HOME/.local/bin:$PATH"
galagent setup

galagent

macOS Apple Silicon

M1, M2, M3, M4, and newer Apple Silicon Macs.

macOS Intel

Older Intel Macs where uname -m prints x86_64.

Linux x86_64

Most Intel and AMD laptops, desktops, and CI runners.

Linux ARM64

ARM servers, Raspberry Pi 4/5 64-bit, and ARM CI runners.

Windows ARM64

Windows on ARM laptops and development machines.

galagent checksums are available at SHA256SUMS.

galactl

macOS Apple Silicon

M1, M2, M3, M4, and newer Apple Silicon Macs.

macOS Intel

Older Intel Macs where uname -m prints x86_64.

Linux x86_64

Most Intel and AMD laptops, desktops, and CI runners.

Linux ARM64

ARM servers, Raspberry Pi 4/5 64-bit, and ARM CI runners.

Windows ARM64

Windows on ARM laptops and development machines.

galactl checksums are available at SHA256SUMS.

Set up your local shell

Create the local auth entry after the CLI is installed. galagent setup opens the browser, shows a short code, and stores the returned API key locally without printing it.

1

Install the binary

Put galagent somewhere on your PATH.

2

Approve browser login

Run galagent setup, confirm the browser code, and select the tenant context.

3

Check your context

Confirm local auth before installing plugins or connecting a worker.

# macOS or Linux install
mkdir -p "$HOME/bin"
os="$(uname -s | tr '[:upper:]' '[:lower:]')"
arch="$(uname -m)"
case "$arch" in
  arm64|aarch64) arch="arm64" ;;
  x86_64|amd64) arch="amd64" ;;
esac
curl -L "https://downloads.galatheus.dev/galatheus/downloads/galagent/2026-05-25-8dacfb0/galagent-${os}-${arch}.tar.gz" | tar -xz -C "$HOME/bin"
chmod 0755 "$HOME/bin/galagent"
export PATH="$HOME/bin:$PATH"
galagent --help
# Windows PowerShell install
New-Item -ItemType Directory -Force "$env:USERPROFILE\bin" | Out-Null
Invoke-WebRequest `
  -Uri "https://downloads.galatheus.dev/galatheus/downloads/galagent/2026-05-25-8dacfb0/galagent-windows-amd64.zip" `
  -OutFile "$env:TEMP\galagent.zip"
Expand-Archive -Force "$env:TEMP\galagent.zip" "$env:USERPROFILE\bin"
$env:Path = "$env:USERPROFILE\bin;$env:Path"
galagent.exe --help
# Browser OAuth device setup
galagent setup

# If your email has access to multiple tenants, be explicit:
galagent --tenant <tenant-id> --workspace <workspace-id> setup
# Confirm setup
galagent auth status --json
galagent whoami --json
galagent workspace list --json

Coordinate local agents

Galatheus does not need to run your code agent. Register the agent name you want to use, then let your local Codex, Claude, CI job, or script claim tickets from the workspace.

# Codex Desktop or local Codex runner
export GALATHEUS_AGENT="codex-$(whoami)-$(hostname -s)"

galagent agent register "$GALATHEUS_AGENT" \
  --kind code \
  --backend codex \
  --mode local \
  --capability app-build \
  --capability app-deploy \
  --capability object.invoke \
  --capability metrics.loss

galagent agent heartbeat "$GALATHEUS_AGENT" --status ready --json
# Watch the workspace queue
galagent agent watch "$GALATHEUS_AGENT" \
  --claim \
  --kind app-build \
  --exec ./agents/handle-ticket.sh
# Create work for an external agent
galagent ticket create \
  --target "$GALATHEUS_AGENT" \
  --kind app-build \
  --app hello-site \
  --title "Create the first version of hello-site" \
  --body "Build a small website app and request deployment." \
  --json
# Local app loop
galagent source checkout --into ./hello-site
cd ./hello-site
galagent app validate . --json
galagent app push . \
  -m "Implement hello-site" \
  --deploy-request \
  --deploy-target "$GALATHEUS_AGENT" \
  --json

agent watch --exec passes claimed ticket JSON on stdin and sets environment variables such as GALACLI_AGENT_NAME, GALACLI_TICKET_ID, GALACLI_TICKET_KIND, and GALACLI_TICKET_APP. Those variable names keep the old prefix during the compatibility window.

Use the dashboard

The dashboard is the human control surface for the same workspace state that galagent exposes to local agents.

1. Sign in

Use the account or invite path sent separately. The onboarding page itself is public; your token and tenant membership are not.

2. Select workspace

Pick the workspace that matches the project you are operating. Workspace selection should match your galagent context.

3. Create tickets

Use tickets for work you want a named external agent to claim. Target the registered agent name.

4. Watch apps

Inspect app status, deploy state, launch URLs, logs, and canvas previews after your agent pushes source.

5. Inspect Objects

Use Objects as reusable capability blocks that agents can discover, invoke, and improve over time.

6. Track loss

Metrics and loss profiles show whether agent work improved the workspace objective.

Useful checks

These commands are safe to run when something feels off.

Auth

Shows local context without printing token material.

galagent auth status --json
galagent config view --json

Workspace

Lists workspaces and summarizes the selected project boundary.

galagent workspace list --json
galagent workspace summary --json

Agent queue

Confirms whether the registered agent has proposed work.

galagent agent status "$GALATHEUS_AGENT" --json
galagent ticket list --target "$GALATHEUS_AGENT" --json