Templates
Scaffold a new workspace from a starter template with qoc init --template, and understand what each template ships out of the box.
Templates are starter workspaces you scaffold with qoc init --template <name> — they ship a pre-wired desk.toml, sample entities, starter issues, and optional schedules so you can have a running workspace in minutes.
What a template contains
Every template is a directory of plain files committed to the Qoc template registry. When you run qoc init --template <name>, Qoc copies the template files into your target directory and tailors the config with your workspace name and any prompts you answer during init.
Templates are not special — after scaffolding they are ordinary workspace files you can edit freely. There is no ongoing link back to the template source.
Files a template typically ships
desk.toml— pre-filled with sensible defaults for the template's use caseentities/— one or more sample entity files showing the expected formatissues/— one or two starter issues that define the initial agent taskschedules/— an optional schedule file if the template is designed for unattended runshouse-rules.md— a starting set of constraints and preferences for the agentresearch/— a placeholder directory (empty or with one orientation note)
Scaffolding a workspace from a template
# List available templates
qoc init --list-templates
# Scaffold into a new directory
qoc init --template equity-watchlist my-equity-desk
# Scaffold into the current directory
qoc init --template macro-research .Built-in templates
| Template name | Best for | Ships schedules |
|---|---|---|
equity-watchlist | Tracking a list of equities; daily morning review issues | Yes — weekday 07:30 |
macro-research | Macro theme tracking; agent writes research notes to research/ | Yes — weekly Sunday 18:00 |
options-expiry | Monitoring open options positions around expiry dates | Yes — weekday 15:45 |
blank | Starting from scratch; minimal config, no sample entities or issues | No |
Customising after scaffolding
Open desk.toml and adjust the [risk] block to match your position limits and allowed venues. Replace the sample entity files in entities/ with your actual instruments or accounts.
The starter issues in issues/ are intentionally generic. Edit them to describe the specific research or monitoring task you want the agent to run. See the self-describing issues guide for the recommended issue format.
If you added a schedule template but want to adjust the cadence, edit the cron field in schedules/ or the [schedule] block in desk.toml directly — standard cron syntax applies.
Templates are versioned
Qoc ships a pinned version of each template with each CLI release. Running qoc init --template <name> always uses the template bundled with your installed version of qoc. Upgrade the CLI with qoc upgrade to get updated template versions.
Share your own templates
You can maintain private templates as plain directories in a git repository and pass a local path or remote URL to qoc init --template. For example: qoc init --template ./internal-templates/fx-desk my-fx-workspace.