Orage

North star

We are working on the most relaxing, agentic working experience.

What it is today

A personal Codex in the cloud. The real Codex agent (codex app-server) runs in a small container, a Svelte app that looks like the Codex desktop and iOS apps talks to it, and a ChatGPT subscription pays for the model.

The product roadmap lists what comes next.

Layout

• apps/server: Node server. Runs Codex, bridges the protocol to the browser, manages workspaces and computers, serves the web app.
• apps/web: the app as a website (SvelteKit, static build).
• apps/site: the public website: the landing page with the waitlist, and this file at /readme.
• packages/protocol: generated app-server protocol types and a client.
• labs/: experiments, such as music and the old Fold harness. Nothing imports them.
• docs/: architecture, protocol map, design measurements, auth, hosting.

Layout has the rules that keep these folders apart.

Run locally

pnpm install
cp .env.example .env   # set ORAGE_PASSWORD and ORAGE_SESSION_SECRET
pnpm dev               # server on :3100, web on :5173 (proxied)
pnpm dev:site          # public website on :5174

Open http://127.0.0.1:5173, enter the password, then Settings, Account, "Sign in with ChatGPT" and follow the device code.

Deploy

See hosting. The short version: the server is a Railway service from branch main with a volume at /data and the variables from .env.example. The public site is a Vercel project built from apps/site.

Verify

pnpm check    # edit loop: lint, format, drift, full Svelte checks, cached TS, all tests
pnpm verify   # before shipping: all checks above and production builds
pnpm doctor:orage # live server, model login, projects, git and installed tools

See project readiness for live checks, setup, known gaps, and the evidence required to prove an agent can ship a change.