DOCUMENTATION

Getting Started

An AI-powered coding assistant using Orca with a React frontend and Elysia backend, managed as a Bun monorepo.

Prerequisites & Installation

  • 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 login dev --config
$ ss whoami --verify
# 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"

Full CLI Command Reference

The ss CLI provides complete access to all Seeyon Studio features from the terminal. Below is the full command list.

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>] ... [--limit <n>]
$ ss audit show <id>
$ ss daemon [--port <port>]
$ ss repo attach --local

E2E Auth Flow

When running outside production with ENABLE_E2E_AUTH=true, CI and agents can use the frontend E2E login URL: