internal/

Package board is the per-project roster of agents the build agent shares with the teammates it spawns.

Package browser holds the server half of the browser takeover bridge: a WebSocket endpoint the ogcode companion browser extension connects to, and the request/response plumbing that turns an agent's tool call into one operation executed in the user's real Chrome tab.

Package codemap produces a compact structural outline of a single source file — every top-level declaration and the line range it occupies — so an agent can jump straight to the region it needs with a bounded read instead of pulling the whole file into context.

Package config loads ogcode's optional file-based configuration: provider base URLs and API keys, the skill sources and permissions, and the live-preview domain, so they can live in a committed/shared file instead of only environment variables.

Package filechange is the read-bookmark gate over file mutations: what each session last read of a file, every change that has landed since, and the durable history of those changes.

Package gitignore matches paths against .gitignore rules.

Package keepawake holds a macOS power assertion while ogcode is doing work that should not be cut short by the display or the system going to sleep — specifically, for the duration of an agent turn.

Package logging sets up ogcode's process-wide slog logger: a size-rotated, owner-only log file that receives everything at the configured level, and a terminal that sees only what the user must act on (errors, by default).

Package mcp connects ogcode to external Model Context Protocol servers declared in the project's ogcode.json under the "mcp" key.

Package memfile is ogcode's per-turn markdown memory: after a turn completes, a structured summary of that turn is written as one dated markdown file under the project's .ogcode/memory/, and an incremental index of that folder lets a read-only recall agent find and read the right file cheaply.

Package modelcatalog persists the model catalogue each provider last reported and seeds a provider registry's in-memory catalogue from that copy.

Package nativehost implements the Chrome Native Messaging host the companion browser extension pairs through: Chrome launches `ogcode native-host` with the port's stdin/stdout bound, and everything the extension needs to find this machine's running ogcode servers — an origin, a websocket URL and a pair token per server — is one "pair" request away.

Package portmap remembers which TCP port each project directory serves on, so starting the same project always reuses the same port instead of drifting to whatever happens to be free at the time (the server walks past a busy port, so without memory a project's port depends on start order).

Package project resolves the stable identity of the workspace a session belongs to.

Package question carries the ask_user round trip: the agent loop registers a batch of questions it cannot answer on its own, blocks until a client replies, and resumes with the answers as the tool result.

Package resource samples this process's own resource usage — CPU, resident memory, Go runtime memory — so the UI can tell the user what ogcode actually costs on their machine.

Package sheet implements spreadsheet type inference: it profiles XLSX/CSV workbooks into per-sheet SheetProfile structures (column types, affinities, min/max, distinct values and sample rows) and the SQLite DDL that matches them.

Package skill implements ogcode's lazy-loaded instruction system.

Package timer is the durable record of one-shot reminders an agent schedules for itself.

Package usage keeps the ledger of model spend and prices it.

Package version provides version information and update checking.

Package worker is the ogcode side of the remote-agent-workers control plane.