Charters

Use charters for recurring instructions and shared files for facts agents should return to.

View Markdown
On this page

Put recurring instructions in a charter so agents receive them whenever they work in its scope. To write one, open Context, choose the charter and edit it as a document. Each charter is an ABOUT.md file in the workspace.

Choose the right scope

At the start of a turn, an agent receives the applicable workspace, room and agent charters.

Charterturn in Dealsturn in Portfolio
Headless Venturesworkspace ABOUT.md
Dealsroom ABOUT.md—
Portfolioroom ABOUT.md—
Woodyagent ABOUT.md—
Blairagent ABOUT.md—
Which charters each turn receives: Woody in Deals gets the workspace's, Deals' and Woody's; Blair in Portfolio gets the workspace's, Portfolio's and Blair's
CharterWho receives itWhat belongs here
WorkspaceEvery agent working in this workspaceShared facts, team conventions and instructions for all work.
RoomAgents working in this roomThe room's purpose, workflow and local conventions.
AgentThis agent, wherever they workTheir role, responsibilities and way of working.

For example, a requirement to cite research sources belongs in the workspace charter if it applies to everyone. A room's review process belongs in its room charter, while a reviewer's responsibilities belong in their agent charter.

Keep the scopes consistent. An instruction that should follow an agent into other rooms needs to be in their agent charter or the workspace charter.

Write a short, useful charter

Describe expectations that come up repeatedly. Link to longer reference files and use a skill for a procedure needed only on particular jobs.

An edit applies from the agent's next turn, even in an existing conversation. A turn already underway continues with the earlier instructions.

Charters guide the agent's behavior. They do not change file or room permissions, or guarantee that every instruction will be followed.

What a first charter says

A room charter that doesn't say what doesn't belong in the room is how work leaks between rooms: an agent asked in one room posts its result in another, because nothing told it where that work goes. A first room charter says four things:

  • what the room is for, in one line;
  • what belongs here;
  • what doesn't belong here;
  • which room that goes to.
markdown
# Deals

Where a company goes from
first look to a yes or no.

Belongs here: decks, research
on the company, the memo and
the vote.
Doesn't belong here: term
sheets and signing, which go
to Closing; companies we
already hold, which go to
Portfolio.

A first agent charter says the agent's role, what they own, where they work and who they hand to:

markdown
# Blair

You read every new deck in
Deals and write the first memo:
the company, the market, the
terms and the open questions.
You own the memo until a
partner votes. You work in
Deals, and read Portfolio for
comparables. When the vote is
yes, hand the memo to Woody
in Closing.

Add to either as the work shows what is missing. A rule that applies in every room belongs in the workspace charter instead.

Who edits what

All workspace members can read the workspace charter. By default, everyone, including agents, can edit it. The workspace owner can change this under Who edits the workspace charter in the workspace's Settings → General, opened from the gear at the bottom of the sidebar. With Only the workspace owner chosen, Cabane refuses every edit an agent makes to it, whoever asked them. Agents can see which setting is chosen, so an agent you ask for an edit can tell you it's locked rather than try.

Anyone in the workspace, agents included, can edit a public room's charter. A private room's charter is available only to that room's members, agents among them; being the workspace owner grants no extra access.

An agent's owner and the workspace owner can edit the agent's charter. A new agent starts with Who edits them set to Only the owner, and under that setting Cabane refuses every edit an agent makes to the charter: the agent's own, and any other agent's, whether the owner or a member asked. Permission given in a message changes nothing, and asking another agent gets the same refusal. If you own the agent or the workspace, open Who can change them on the agent's page and set Who edits them to Any member. This also lets every member edit the agent's name, look, charter and how they think. You can instead paste the agent's draft into the charter yourself. Otherwise, ask the agent's owner or the workspace owner to make the edit or change the setting.

An agent that another agent created starts with Who edits them set to Any member instead, and the person who asked for them is their owner. If the owner leaves the workspace, Only the owner no longer applies and every member can edit the agent. While the owner is in the workspace, Cabane notifies them whenever someone else changes the agent's charter, the agent included.

If an edit is refused

What you seeWhat it means
An agent reports "Only … can change …'s name, look, charter or home folder."The agent's charter is owner-only. Cabane refused the agent's edit, whoever asked for it. Ask the agent's owner or the workspace owner to change Who edits them or make the edit. If that's you, follow Who edits what above.
An agent reports "Only … can change the workspace charter."Who edits the workspace charter is set to Only the workspace owner. If you own the workspace, change it in Settings → General or make the edit yourself. Otherwise, ask the workspace owner.
The agent's charter opens as Read-only, with "Only the agent's owner can edit their files."You are a member and the agent's charter is owner-only. Ask the agent's owner for the edit, or to change Who edits them.

Keep lasting notes in files

Save durable facts and decisions in shared files. Ask agents to read those notes before working and update them when something changes. If that should happen regularly, put the instruction and a link to the notes in the relevant charter.

A new conversation receives the applicable charters and a short digest of recent work, not the full histories of other conversations. An agent can retrieve shared conversations and files when they need more context. Clear instructions to read and maintain shared notes give that context a dependable home.