Workspaces

A workspace is the local directory that is your trading desk — a folder of plain files that your AI agents read, write, and version-control on your behalf.

A reference for every directory and file in a Qoc workspace, with notes on format, ownership, and when each is read or written.

An entity is a tracked ticker or company stored as a markdown file in entities/. It is the agent's durable memory for everything it has learned about that name.

The inbox/ directory is where external events arrive as files — broker fills, price alerts, webhook payloads, and system messages. The agent triages them on each run.

Issues are the desk's task queue — markdown files in issues/ that represent research questions, trade ideas, or operational tasks the agent is working through.

A self-describing issue carries enough context — goal, constraints, acceptance criteria, and links — for an agent to pick it up and complete it without further instruction.

How workspace settings and context are injected into the agent session at run time, including precedence rules and per-workspace scoping.

How Qoc exposes a scoped set of qoc commands and workspace files into the agent runtime so the agent can research, propose trades, and write results back safely.

Run workspaces on a cron cadence so the agent picks up open issues unattended and writes results back as files and inbox items.

Scaffold a new workspace from a starter template with qoc init --template, and understand what each template ships out of the box.

Configure inbound HTTP webhooks that create inbox items or trigger workspace runs when an external event fires.