Skip to main content
Version: 3.1

Operaide Code

Operaide Code is a terminal coding agent for building Operaide apps. It behaves like a generic CLI coding assistant, but ships the Operaide handbook embedded in the binary so you do not re-teach the Aktor framework every session.

Beta

Operaide Code is under active construction. The interface, defaults, and tool set may change between releases. Use it for app development, not for production automation.

What it is​

Operaide Code is a single Go binary that runs in your terminal. You point it at an app folder and ask it, in plain English, to read, write, and validate Reaktor code. It reaches an LLM through Operaide Studio's proxy or through your own provider keys.

Three things distinguish it from a generic coding agent:

  • Embedded handbook. The same handbook you are reading is baked into the binary. The agent searches it before touching any framework call (aktorXxx, registerXxxReaktorDefinition, AI / database / mail integration, deploy semantics).
  • Three approval modes. Plan mode is read-only; normal mode asks before every change; auto mode runs silently. You switch with one keystroke or a slash command.
  • Working-directory sandbox. Tools resolve every path relative to the directory you launched in. Anything that escapes is refused, even when symlinks are involved.

When to use it​

Reach for Operaide Code when you want a terminal-driven flow:

  • Iterating on a Reaktor in a Studio workspace and you prefer a CLI to the in-editor AI agents.
  • Running outside Studio (laptop, CI script, ssh session) with your own provider keys.
  • Building an App UI under public/ where a back-and-forth chat is faster than hand-edits.

If you want an in-browser agent embedded in the editor, see Vibe Coding with Integrated AI.

How it stays Operaide-aware​

The system prompt tells the model it has no built-in framework knowledge and must call search_handbook first whenever the turn touches a framework concept. The handbook content is mirrored from the published handbook into the binary at build time, so the agent's reference matches the version of the handbook shipped with that release.

The agent also reads your package.json, detects @operaide/* dependencies, and lists the .reaktor.ts files it can see, so its first turn already knows what kind of app it is in.

Where to go next​

If you are inside an Operaide Studio workspace, start with Running in Operaide Studio. For a laptop install with your own keys, see Running Locally. For the agent's behaviour and tool set, see Modes and Tools. For tables of slash commands, key bindings, and config keys, see Command Reference.