Context Circuit
Template

What the workspace template contains

The shared workspace structure your coding host reads and your project keeps.

Template 2.5.0

The shipped structure

AreaPurpose
AGENTS.md and host entry filesStanding instructions and human control boundaries.
.agents/skills/Procedures for workspace setup, knowledge, intents, plans, worktrees, workers, delivery, and completion.
workspace.yaml and members.yamlProject identity, repository model, and roster.
context/Durable knowledge, optional catalog, and glossary.
intent/ and plans/Human-readable outcomes and implementation plans.
.context-circuit/Product pins, the launcher (cli and cli.ps1), per-member ID reservations, role preferences, and reference documentation.
.ignoreKeeps /sources/ out of ripgrep-based search.
.claude/settings.jsonAllows both launcher commands in Claude Code without a prompt.

What is created locally

Member selection, checkout bindings, native agent definitions, the Claude Code attribution setting in .claude/settings.local.json, working copies, and runtime files are machine-local. They are not a portable snapshot of another developer's environment.

The published template repository's README, license, changelog, contribution and security pages, and artwork do not enter a fresh workspace archive. The project's own README is written at initialization.

A workspace that already has .claude/settings.json takes a template update's entries merged in entry by entry, keeping every entry it added, rather than replacing the file.

Read local versus shared configuration.

On this page