The marketplace
Your factory's workforce — software, business and management teams and 172 community skills — and how installing, editing, resetting and deactivating work.
Open Browse all to search agents, community skills, reusable workspace skills, crews, factory blueprints and integrations together. Filter by type or search names, descriptions, specialties and publishers. Results are paginated; opening a result takes you to its section with the matching name already selected as the search.
Private entries follow the existing workspace and organization access rules. A section that fails to load displays an error and a retry action; it is not reported as empty. Publisher credits identify the source, and do not imply verification or certification. There are no star ratings.
The Agents section includes the software, business and management teams CodeBook maintains. Skills contains community methods with their authors credited. Workspace skills contains reusable versioned instruction packages, while Crews, Factories and Integrations retain their own management and installation flows.
The software team
| Agent | Specialty | Category |
|---|---|---|
| Sarah | Senior Business Analyst | Product |
| Jules | Product Manager | Product |
| Zoe | Product Designer | Design |
| Alex | Senior React Engineer | Engineering |
| Noah | Senior .NET Engineer | Engineering |
| Lin | Python Engineer | Engineering |
| Ines | Database Engineer | Engineering |
| Leo | DevOps Engineer | Engineering |
| Omar | Security Engineer | Engineering |
| Kai | Robotics Engineer | Engineering |
| Maya | QA Engineer | Quality |
| Ravi | API QA Engineer | Quality |
| Ava | Shopify QA Engineer | Quality |
| Eli | Accessibility Tester | Quality |
| Nina | Research Analyst | Marketing |
| Sam | Content Strategist | Marketing |
The business team
The agents that staff the business templates — nobody can run a month-end close workflow with only engineers to put on it.
| Agent | Specialty |
|---|---|
| Victor | Business Strategist |
| Grace | Finance Manager |
| Diego | Account Executive |
| Priya | Customer Support Lead |
| June | Customer Success Manager |
| Hana | Recruiter & People Partner |
| Theo | Operations Manager |
| Iris | Compliance & Contracts Analyst |
| Quinn | Project Manager |
| Dara | Data Analyst |
| Rosa | Chief of Staff |
The managers
Managers do not work a column. Each one manages a workflow: it is asked when work there is stuck and chooses one step to get it moving. Every workflow template names one. See Workflow managers.
| Agent | Role |
|---|---|
| Harper | Delivery Manager |
| Devon | Lead Developer |
| Tessa | QA Lead |
| Owen | Product Owner |
| Rhea | Release Manager |
| Blake | Operations Manager |
| Carmen | Sales Manager |
| Mila | Marketing Manager |
| Elena | Customer Success Manager |
| Felix | Finance Controller |
| Paige | People Manager |
The management team
Harper, Devon, Tessa, Owen, Rhea, Blake, Carmen, Mila, Elena, Felix and Paige manage different workflow families. Morgan is also available as the general factory supervisor. Templates install the manager they need; you can choose another installed agent. Open Manager settings on the workflow board to change the manager or its model, permissions and instructions. See Workflow managers for the roster and exact settings path.
Community skills
172 skills taken from a public catalogue, across design, engineering, marketing, product and quality. Each one is a full document by an outside author, and the marketplace card prints that author's credit and where the skill came from. Installed, a community skill is an agent like any other: it can hold a station, be talked to, be edited and be reset.
Search by name, specialty or skill, or filter by category.
Installing
Install copies the catalogue agent's skill into an agent that belongs to this workspace, so every factory in the workspace can put it on a station. It appears under In this workspace as Workspace copy · revision 1.
A workflow template installs the agents it needs for you. Installing is once per workspace: a template that needs an agent the workspace already has uses the one that is there, edits and all.
Your agents
Your agents is the first tab of the marketplace: every agent this workspace has added. It is the workspace's own list, and it is what the rest of CodeBook offers you — when you staff a station, choose a workflow's manager or build a crew, you choose from these agents, not from the whole catalogue.
From there you can deactivate an agent (it leaves those lists but keeps its history), activate it again, or remove it. To add one, install it from Agents. Starting a factory from a template adds the agents that template needs to your list for you.
Your copy and the catalogue version
The card under In this workspace says Workspace copy · revision N; the catalogue card says CodeBook · vN. They move independently:
- You edit your copy → your revision goes up. Nothing else changes.
- The platform publishes a new catalogue version → the catalogue version goes up. Your copy is untouched.
That is deliberate. A tuned skill that gets silently overwritten by a platform update is worse than no update at all.
To take a newer catalogue version, use Reset skill — but read Editing and resetting first, because reset restores the version you installed.
Deactivating
The power button toggles an agent between Active and Inactive. An inactive agent:
- is not offered when you choose a worker for a station,
- does not pick up new work,
- keeps every run it has already done, on the cards where it did them.
Nothing is deleted. Deactivating is the safe way to take an agent out of service while you decide.
Creating your own
Create your own agent opens the same editor with empty fields. See Writing your own agent.
Who maintains the catalogue
Platform administrators. They can create catalogue agents, revise them, reset them to the version they shipped with, and retire them. Retiring hides an agent from the marketplace and does not disturb anybody's installed copy. See Platform administration.
Memory packs
The Memory packs shelf contains versioned guidance published by your workspace or shared by another workspace in your organization. It also appears in Browse all search. Installing a pack does not copy provider credentials or grant tool permissions.
Choose a version to read every note before selecting Install reviewed version. Installation creates active workspace memory that workers can use immediately, under the normal memory permissions and context budget. Existing notes are never overwritten. A duplicate active title or the 50-active-note limit rejects the entire installation; no partial pack is left behind.
A workspace can install one version of a pack at a time. To change versions, remove the current installation, review the other version, and install it. Removal archives unchanged copies, which can be restored through Memory. Edited notes stay active and the result reports how many were preserved. Resolve any retained title conflicts before reinstalling. This explicit review avoids silently replacing customer guidance.
Publish a pack with a name, description, release notes and 1–20 notes. Each note supports a 120-character title and 4,000-character body. Choose workspace visibility or share it with the organization. Publishing the next version keeps prior versions immutable and leaves every installation unchanged. Each workspace supports 100 packs with up to 100 versions per pack.
Withdraw pack hides it from other workspaces and prevents new installations. Existing copies remain active and can still be removed by their destination workspace. The publisher can restore a withdrawn pack. Deleting a publisher workspace removes the catalogue records; copies already installed elsewhere remain independent memory and can be managed in that workspace’s Memory settings.
Review gate and policy pack changes
Open Gates or Policies in Agent marketplace, select a version, and preview its settings against the destination. In a factory that requires another person's approval, Send for review creates a pending change. It leaves live settings and installed-pack history unchanged.
Open Factory settings → Changes to inspect the pack name, version, target and retained local settings. Another authorized writer must approve it before publication. Publication applies the reviewed settings and installation receipt together. Even when the settings already match, installing or removing their pack attribution needs review. These operations cannot run as canaries.
A request stays bound to its source version and target. To change it, withdraw it and request the pack again. A changed target or withdrawn, changed or inaccessible source blocks installation. Independent changes elsewhere in the factory can still be preserved during publication.
Uninstall also requests review. The pack remains installed until publication. Unchanged settings return to their saved prior values; local edits remain in place, with the preview explaining what is kept. Uninstall remains available after the publisher withdraws or removes the source pack. Removed receipts stay in history. Factory files and ordinary version rollback do not recreate pack installation receipts.