Optimus

Control panel for cloud browser automation. Users describe a task in English, Optimus drives a real browser on Browser Use Cloud, and every run is recorded with steps, screenshots, tokens, and cost.

Two frontends share one backend:

Web — Next.js app on a public domain, OAuth sign-in (Google + Microsoft).
TUI — Ink CLI, reaches the web app’s API via a personal access token.

Documentation map

Section	What’s in it
Getting started	Install, run locally, understand the moving parts.
Concepts	Runs, steps, the status machine, auth, cost, URL guard.
Apps	The Next.js web app and the Ink TUI — usage, env, conventions.
Packages	Hand-written guides for the six shared workspace packages.
API reference	Auto-generated TypeScript symbol-by-symbol reference.
Operations	Deploying to Railway + Supabase, troubleshooting.
Contributing	Branch + commit conventions, coding standards, docs workflow.

Monorepo layout


apps/
  web/            Next.js App Router — auth, API, run orchestration, history UI
  tui/            Ink TUI — thin HTTP client
  docs/           This site (Nextra + Next.js)
packages/
  core/           Pure TS domain: types, Zod schemas, URL guard, cost, status machine
  api-client/     Typed HTTP + SSE client (shared by TUI and web)
  browser-use/    Wrapper around Browser Use TS Cloud SDK
  db/             Drizzle schema + repositories (server-only)
  auth/           Better Auth config + PAT helpers
  config/         Shared tsconfig presets
legacy/           Original Python Textual app — read-only during migration

Where things live

Source of truth for domain types: @optimus/core.
Database schema: @optimus/db.
Browser automation backend: @optimus/browser-use, wrapping Browser Use Cloud.
Auth (sessions + PATs): @optimus/auth, built on Better Auth.
Production runbook: Operations / Deployment.