DOCUMENTATION

Getting Started

Seeyon Studio is an AI-powered coding workspace backed by Orca, with a React web app, a Bun + Elysia server, and the non-interactive ss CLI.

Connect the CLI

  1. Sign in at studio.seeyon.chat.
  2. Open Settings › API key and mint your personal ss_ key.
  3. Verify the key and save it to your local CLI config:
$ ss --server https://studio.seeyon.chat \ --api-key <key> --config whoami --verify

--config stores the server URL and key, so later commands can drop both flags.

Self-Hosting

  • Bun 1.2+
  • Orca agent-manager running locally on port 2644
  • PostgreSQL database URL in DATABASE_URL
# Install dependencies
$ bun install
# Start dev server
$ bun run dev

This starts both the backend (Elysia) on port 5124 and frontend (Vite+React) on port 5123.

Workspaces

frontend

React + Vite + Tailwind CSS browser app.

server

Bun + Elysia API and websocket server.

cli

Non-interactive ss CLI client.

CLI Smoke Test

Here are some of the core commands you can run using the ss CLI:

# Auth & Identity
$ ss whoami --verify
$ ss api-key
# Tasks & Chat
$ ss task create "Fix flaky auth test"
$ ss "hello"
# Repo Upload & Diff
$ ss --chat <id> repo upload src/
$ ss --chat <id> diff --name-only
$ ss --chat <id> patch apply
# Verification
$ ss verify --quick
$ ss --chat <id> report .seeyon-studio/verify-result.json
# Git & PRs
$ ss git commit -m "fix: updated auth"
$ ss git push --set-upstream
$ ss git pr create --title "Fix Auth" --body "Fixes token refresh"

Full CLI Command Reference

The ss CLI provides complete access to all Seeyon Studio features from the terminal. Run ss --help for global options.

Auth & Identity

$ ss login dev
$ ss whoami [--verify]
$ ss api-key [refresh|delete]

Tasks & Chats

$ ss task create "task title"
$ ss task list
$ ss task status <id> [open|running|blocked|done|cancelled]
$ ss task verify <id> [--quick]
$ ss task diff <id> [--name-only]
$ ss task patch download <id> --out <local-path>
$ ss task git attach <id>
$ ss task approvals <id>
$ ss task approval request <id> --type <type> --title "title" [--detail "detail"]
$ ss task approval approve/reject <approval-id>
$ ss task open <id>
# Raw Chats
$ ss chats
$ ss chats create
$ ss [--chat <id>] "prompt text"

Repo Intelligence & Sync

$ ss repo info
$ ss repo index
$ ss --chat <id> repo status [local-path]
$ ss --chat <id> repo upload <local-path> [--changed] [--force]
$ ss --chat <id> repo download [remote-path] --out <local-path> [--changed] [--force]
$ ss --chat <id> diff [--name-only]
$ ss --chat <id> patch download --out <local-path>
$ ss --chat <id> patch apply [--force]

Remote Workspace Files

$ ss --chat <id> files ls [path]
$ ss --chat <id> files read <path>
$ ss --chat <id> files write <path> <content>
$ ss --chat <id> files create <path>
$ ss --chat <id> files mkdir <path>
$ ss --chat <id> files delete <path>
$ ss --chat <id> files rename <old-path> <new-path>

Verification & Fixes

$ ss verify [--quick] [--chat <id>]
$ ss --chat <id> report [path]
$ ss --chat <id> fix --from-last-error

Git & PR Workflow

$ ss git status
$ ss git diff [--name-only]
$ ss git branch create <name>
$ ss git commit -m "message" [--force]
$ ss git push [--set-upstream]
$ ss git pr create --title "title" --body "body" [--draft]
$ ss git checks

Audit & Local Daemon

$ ss audit list [--scope <scope>] [--action <action>] [--status <status>] [--limit <n>]
$ ss audit show <id>
$ ss daemon [--port <port>]
$ ss repo attach --local

E2E Auth Flow

When a self-hosted backend runs outside production with ENABLE_E2E_AUTH=true, CI and agents can sign in without a password:

$ ss login dev --config
# Browser login on the local frontend (port 5123)
/e2e/login
/e2e/login?redirect=/tasks
/e2e/login?email=admin@example.com&role=Coder&redirect=/repo