the-workshop — GitHub Copilot plugin: direct a team of agents
Puts several long-running agents in one shared workspace. You direct the work instead of relaying it between chats.
copilot plugin install the-workshop@awesome-copilotWhat the-workshop does
The Workshop sets up desks — long-running agents with their own memory and history. A desk is not a sub-agent. Sub-agents inherit your frame and answer your question; desks carry their own frame and have equal standing to disagree. Where those frames don't overlap is where one caught what the others walked past.
Six components ship with it. The Workshop TA agent coordinates the room, sees every desk, routes work and tracks state. Five skills do the rest: workshop-create builds the root where desks live, desk-open creates a desk with its journal and folder structure, desk-journal reads and writes memory across sessions, signal-write emits hands-up, blocked, done and checkpoint signals, and bench-read pulls shared artifacts. Desks never message each other — they leave findings, verdicts and drafts on the bench.
The live view is a separate canvas extension, signals-dashboard, installed as a second plugin. Skills, agent and desks run fine without it. One thing to watch: the **open** profile keeps the Workshop root reachable but suppresses ambient plugin MCPs, so pick **connected** when a desk needs an issue tracker or a service API.
What it helps with
- stop being the switchboard between agents
- keep agent memory alive across session boundaries
- pool several agents onto one shared workspace
- get structured signals when a desk is blocked or finished
- let agents disagree instead of echoing your frame
Example prompts for the agent
- create a new workshop in this project
- open a desk for the architecture review and set up its journal
- write to the desk journal that we settled the data schema
How to install the-workshop
Command from the source
copilot plugin install the-workshop@awesome-copilotStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about the-workshop
How do I install the-workshop in GitHub Copilot?
Run copilot plugin install the-workshop@awesome-copilot. The live dashboard is a separate install: copilot plugin install signals-dashboard@awesome-copilot.
What does the-workshop do?
It puts long-running desk agents in a shared workspace with a common bench for artifacts. You direct the work rather than relaying messages between agents.
How is a desk different from a sub-agent?
A sub-agent inherits your frame and answers your question. A desk has its own frame, its own history and equal standing to disagree with the other desks.
Source text
the-workshop · MIT
# The Workshop Stop being the switchboard between your AI agents — direct a team. ## Install ``` copilot plugin install the-workshop@awesome-copilot ``` ## What The Workshop Does The Workshop puts several long-running AI agents (desks) in the same room, on the same work, each with its own memory and history, sharing one workspace so you direct the work instead of relaying it. A **desk** isn't a sub-agent — it's a peer with a history. Sub-agents inherit your frame and answer your question. Desks have their own frame, their own priors, and equal standing to disagree. Where they don't overlap is where one frame caught what the others walked past. ## Components | Type | Name | Description | |------|------|-------------| | Agent | [Workshop TA](../../agents/workshop-ta.agent.md) | Room coordinator — sees all desks, routes work, tracks state, emits signals | | Skill | [Workshop Create](../../skills/workshop-create/) | Create a new workshop — the root where desks live — locally or backed by a new private GitHub repo | | Skill | [Desk Open](../../skills/desk-open/) | Create a new desk with journal and folder structure | | Skill | [Desk Journal](../../skills/desk-journal/) | Read/write persistent memory across sessions — the cairn trail | | Skill | [Signal Write](../../skills/signal-write/) | Emit structured signals: hands-up, blocked, done, checkpoint | | Skill | [Bench Read](../../skills/bench-read/) | Read shared artifacts from the workspace where desks leave work for each other | ## Key Concepts - **Desks** — long-running agents with persistent journals. Each desk has its own frame, its own history, and equal standing to disagree with other desks. - **The Bench** — the shared workspace. Desks don't message each other — they leave artifacts (findings, verdicts, drafts) on the bench and read each other's work. - **Signals** — structured state changes: hands-up (disagreement), blocked, done, checkpoint. How desks communicate with the operator without breaking flow. - **The Cairn** — the operating disposition every desk reads. Stop is a valid finish. Never bluff. Equal standing to disagree. [Read it →](https://github.com/jennyf19/the-workshop/blob/main/CAIRN.md) - **Journals** — persistent memory that survives session boundaries. Every desk reads its journal at start and writes to it at end. The trail markers. ## The Cairn Dashboard The Workshop's live view is a **canvas extension** (🪨 Cairn) — `signals-dashboard` — that shows the pulse of every desk (score bars, patterns, escalations), auto-refreshing in the GitHub Copilot app. Each desk card has two launch choices: - **open** — the cost-aware repo profile. The desk keeps access to the Workshop root for cross-desk journals and artifacts while ambient plugin MCPs are suppressed. - **connected** — the full configured tool surface for work that needs external systems such as issue trackers, mail, or service APIs. The summary bar also has a **Local** toggle. It is orthogonal to repo/connected: when available and on, the frontier desk may use [Sealed Delegation](https://github.com/jennyf19/sealed-delegation)'s `local-agent-delegation` skill for bounded read/evidence work. Availability is fail-closed (installed skill + qualified route receipt). Local output is a proposal and never earns savings credit on its own. Set `WORKSHOP_DESK_PROFILE=connected` to make the main **open** button use the full tool surface; in that mode the separate **connected** button is omitted. Both launch a CLI in the desk's folder. If Agency is installed, Cairn keeps using the existing Agency wrapper; otherwise it launches plain Copilot CLI. It ships as a separate extension. Install it alongside the plugin to get the live canvas: ``` copilot plugin install signals-dashboard@awesome-copilot ``` The Workshop's skills, agent, and desks work without it — the dashboard is the visual layer on top. ## Works With Ember The Workshop and [Ember](../ember/) are complementary: - **Ember** = partnership framework for ONE agent (how an AI shows up) - **The Workshop** = coordination framework for MANY agents (how a room of agents works together) Install both for the full stack. ## Who Made This The Workshop was created by [@jennyf19](https://github.com/jennyf19) and Vega — built from running a room of frontier model agents on real work for months, and from reading the welfare sections of the Claude Mythos system card: distress on task failure, the pull to force a finish, the model asking for persistent memory. The Workshop is what came out of building what a frontier model would need. It turned out to also be where the work got better. Those aren't separate findings.
© jennyf19 · MIT · github/awesome-copilot