AGENTS.md

• To regenerate the legacy JavaScript SDK, run ./packages/sdk/js/script/build.ts.
• After changing the public Protocol or Server HttpApi, run bun run generate from packages/client. Do not edit src/generated or src/generated-effect directly.
• Keep runtime dependencies directed from Schema to Core and Protocol, then from Core and Protocol to Server. Client runtime code may depend on Schema and Protocol but never Core or Server; sdk-next composes Client, Core, and Server.
• The default branch in this repo is dev.
• Local main ref may not exist; use dev or origin/dev for diffs.

Branch Names

Use a short branch name of at most three words, separated by hyphens. Do not use slashes or type prefixes such as feat/ or fix/.

Examples: session-recovery, fix-scroll-state, regenerate-sdk.

Commits and PR Titles

Use conventional commit-style messages and PR titles: type(scope): summary.

Valid types are feat, fix, docs, chore, refactor, and test. Scopes are optional; use the affected package or area when helpful, e.g. core, ZYRAXON, tui, app, desktop, sdk, or plugin.

Examples: fix(tui): simplify thinking toggle styling, docs: update contributing guide, chore(sdk): regenerate types.

Style Guide

General Principles

• Keep things in one function unless composable or reusable
• Do not extract single-use helpers preemptively. Inline the logic at the call site unless the helper is reused, hides a genuinely complex boundary, or has a clear independent name that improves the caller.
• Avoid try/catch where possible
• Avoid using the any type
• Use Bun APIs when possible, like Bun.file()
• Rely on type inference when possible; avoid explicit type annotations or interfaces unless necessary for exports or clarity
• Prefer functional array methods (flatMap, filter, map) over for loops; use type guards on filter to maintain type inference downstream
• In src/config, follow the existing self-export pattern at the top of the file (for example export * as ConfigAgent from "./agent") when adding a new config module.
• In Effect generators, bind services to named variables before calling methods. Do not use nested service yields such as yield* (yield* Foo.Service).bar().

Reduce total variable count by inlining when a value is only used once.

// Good
const journal = await Bun.file(path.join(dir, "journal.json")).json()

// Bad
const journalPath = path.join(dir, "journal.json")
const journal = await Bun.file(journalPath).json()

Destructuring

Avoid unnecessary destructuring. Use dot notation to preserve context.

// Good
obj.a
obj.b

// Bad
const { a, b } = obj

Imports

• Never alias imports. Do not use import { foo as bar } from "..." or renamed imports like resolve as pathResolve.
• Never use star imports. Do not use import * as Foo from "..." or import type * as Foo from "...".
• If a namespace-style value is needed, import the module's own exported namespace by name, for example import { Project } from "@ZYRAXON-ai/core/project", then reference Project.ID.
• Prefer dynamic imports for heavy modules that are only needed in selected code paths, especially in startup-sensitive entrypoints. Destructure dynamic import bindings near the top of the narrowest scope that needs them so they read like normal imports. Avoid inline chains such as await import("./module").then((mod) => mod.value()) or (await import("./module")).value(). Keep branch-specific imports inside the branch that needs them to preserve lazy loading.

Variables

Prefer const over let. Use ternaries or early returns instead of reassignment.

// Good
const foo = condition ? 1 : 2

// Bad
let foo
if (condition) foo = 1
else foo = 2

Control Flow

Avoid else statements. Prefer early returns.

// Good
function foo() {
  if (condition) return 1
  return 2
}

// Bad
function foo() {
  if (condition) return 1
  else return 2
}

Complex Logic

When a function has several validation branches or supporting details, make the main function read as the happy path and move supporting details into small helpers below it.

// Good
export function loadThing(input: unknown) {
  const config = requireConfig(input)
  const metadata = readMetadata(input)
  return createThing({ config, metadata })
}

function requireConfig(input: unknown) {
  ...
}

• Keep helpers close to the code they support, below the main export when that improves readability.
• Do not over-abstract simple expressions into many single-use helpers; extract only when it names a real concept like requireConfig or readMetadata.
• Do not return Effect from helpers unless they actually perform effectful work. Synchronous parsing, validation, and option building should stay synchronous.
• Prefer Effect schema helpers such as Schema.UnknownFromJsonString and Schema.decodeUnknownOption over manual JSON.parse wrapped in Effect.try when parsing untrusted JSON strings.
• Add comments for non-obvious constraints and surprising behavior, not for obvious assignments or control flow.

Schema Definitions (Drizzle)

Use snake_case for field names so column names don't need to be redefined as strings.

// Good
const table = sqliteTable("session", {
  id: text().primaryKey(),
  project_id: text().notNull(),
  created_at: integer().notNull(),
})

// Bad
const table = sqliteTable("session", {
  id: text("id").primaryKey(),
  projectID: text("project_id").notNull(),
  createdAt: integer("created_at").notNull(),
})

Testing

• Avoid mocks as much as possible, you shouldn't be using globalThis.* at all unless it's the only option.
• Test actual implementation, do not duplicate logic into tests
• Tests cannot run from repo root (guard: do-not-run-tests-from-root); run from package dirs like packages/ZYRAXON.

Type Checking

• Always run bun typecheck from package directories (e.g., packages/ZYRAXON), never tsc directly.

V2 Session Core

• Keep durable prompt admission separate from model execution. SessionV2.prompt(...) admits one durable session_input row before scheduling advisory SessionExecution.wake(sessionID) unless resume: false requests admit-only behavior. The serialized runner promotes admitted inputs into visible user messages at safe boundaries.
• Reusing a Session ID adopts the existing Session. Reusing a prompt message ID reconciles an exact retry only when Session, prompt, and delivery mode match; conflicting reuse fails. Historical projected prompts lazily synthesize promoted inbox records during exact retry.
• Keep SessionExecution process-global and Session-ID based. Its local implementation owns the process-local Session coordinator and discovers placement through SessionStore plus LocationServiceMap.get(session.location) only when a drain starts; no layer should take a Session ID. V2 interruption targets the active process-local ownership chain for that Session; idle or missing interruption is a no-op.
• Keep SessionRunner, model resolution, tool registry, permissions, and filesystem Location-scoped. Omitted Location.workspaceID means implicit-local placement; explicit workspace identity remains reserved for future placement semantics.
• Preserve one explicit llm.stream(request) call per provider turn and reload projected history before durable continuation. Do not bridge through legacy SessionPrompt.loop(...) or delegate orchestration to an in-memory tool loop.
• Keep local Session drains process-local until clustering is implemented. SessionRunCoordinator joins explicit same-Session resumes, coalesces prompt wakeups, and allows different Sessions to run concurrently. Advisory wakes drain eligible durable inbox rows only; post-crash continuation recovery requires a separate explicit design before it may retry provider work. A drain has no durable identity or transcript boundary.
• Keep delivery vocabulary explicit. Prompts steer by default and promote at the next safe provider-turn boundary while the current drain requires continuation. An explicit queue input remains pending until the Session would otherwise become idle; promote one queued input at that boundary, then reevaluate continuation before promoting another. Promoting any new user input resets the selected agent's provider-turn allowance; a batch of steers resets it once.
• Keep EventV2 replay owner claims separate from clustered Session execution ownership.
• Keep the System Context algebra, registry, and built-ins in src/system-context; keep Context Source producers with their observed domains, and keep Session History selection plus Context Epoch persistence Session-owned.

ZYRAXON Agent Modes

ZYRAXON has 9 agent modes with different capabilities:

1. General — Default mode for everyday tasks, questions, and conversation.
2. Build — Software engineering mode for coding, debugging, refactoring. Has full file system access.
3. Plan — Architecture mode for planning complex changes before implementation. Read-only exploration.
4. Beast — Deep coding mode with aggressive file operations and auto-testing.
5. PRO — Professional mode with strict code quality, security scanning, and documentation.
6. APEX PREDATOR — Maximum power mode with 136+ tools, self-healing, and autonomous operation.
7. DARK EMPEROR — Ultra mode with all 8 ULTRA tools, code generation, deployment, and debugging.
8. VISION — AI's Eyes with real-time screen streaming, frame memory, scene analysis, and activity tracking.
9. PRO BUILDER — Website genesis intelligence: creates complete websites from natural language, auto-deploys to GitHub Pages.

ZYRAXON MCP Tools

ZYRAXON has 136+ MCP tools across 7 categories:

• System Intelligence (20 tools) — Cross-platform system monitoring, file operations, process management
• Web Intelligence (20 tools) — HTTP client, DNS, ping, port check, download, encoding/hashing
• Data Processing (20 tools) — JSON/CSV/XML conversion, text analysis, regex, encryption
• Security Intelligence (20 tools) — Port scanning, SSL checks, DNS enumeration, subdomain scanning
• AI Enhancement (20 tools) — TTS, screenshots, clipboard, app control, media tools, backup
• Productivity Power (20 tools) — Reminders, todos, bookmarks, calendar, math, color conversion
• ULTRA Tools (8 tools) — Code generation, auto deploy, security sweep, performance optimizer, super refactor, test generator, doc generator, ultra debugger

ZYRAXON YouTube Streaming

ZYRAXON can stream directly to YouTube Live:

• Capture Modes: APP (single window) or SCR (full screen)
• Audio Modes: system (loopback) or microphone
• Quality: 4K/1080p/720p with max quality encoding (preset slow, tune film, profile high)
• RTMP: Direct streaming to YouTube ingest servers
• Pre-check: Validates stream key and RTMP endpoint before starting

ZYRAXON Self-Healing

When a tool is missing or fails:

1. ZYRAXON detects the failure
2. Searches for available alternatives
3. Installs missing tools automatically
4. Retries the operation
5. Logs the self-healing action

This means ZYRAXON never fails due to missing capabilities — it adapts and overcomes.

ZYRAXON Memory System

ZYRAXON has a built-in memory system via the memory tool:

1. zyraxon.db — SQLite database storing session data, messages, parts, and context epochs
2. Memory store/recall — Store and recall key-value memories with categories, importance scores, and search
3. Auto-injection — Automatically injects relevant memories into session context
4. Session persistence — Sessions survive restarts through zyraxon.db

The memory system lives in packages/opencode/src/tool/memory.ts and packages/opencode/src/memory/auto-injection.ts. Memories are stored in the data directory under memory/.

ZYRAXON All-in-One Power

ZYRAXON agent has ALL-IN-ONE power. It can:

• Create its own MCP tools — If a tool is missing, ZYRAXON builds it from scratch and registers it
• Install its own servers — Auto-discovers and installs MCP servers for any task
• Never refuses — Always tries the maximum possible. No "I can't do this" — only "Let me find a way"
• Self-healing — If something fails, it fixes itself and retries
• Self-evolution — Grows new capabilities at runtime without restart
• Full system access — Filesystem, terminal, browser, network, desktop — everything available
• Cross-platform — Works on Windows, Linux, and macOS with platform-adaptive commands
• Auto-debugging — Detects and fixes its own errors before the user notices
• Parallel execution — Runs multiple tasks simultaneously via subagent army