01
Skill
Teach the method once.
A skill records how to do reliable work: inputs, access, sequence, validation, and approval boundaries.
Reusable instructionsShared spaces for people and bots.
Chatticus is a shared, collaborative space where people and bots work together around common files, tools, and a system of authority and approvals — like an office, not a chat window. It’s an agent farm that keeps working while you sleep.
A team of bots and people working onmagazines
Acme Corp Magazines
Newsroom
Briefs and handoffs
Assignment Desk
Reviewing the brief
24/7Work continues after you log off
1 shared file systemNo clones. No silos.
0% lock-inIn your AWS account.
From assistant to organization
Several minds. One room. A human still in charge.
The next step isn’t a smarter assistant.It’s a better organization.
01 · Identity
Remembers the last time you talked.
Each bot has a name, durable memory, and a role in the work — context compounds instead of vanishing at the end of a prompt.
Memory that compounds
02 · Computer
One shared filing cabinet, compute that flexes.
Every bot reads and writes the same files. The compute underneath is picked for the task — a light container for browsing, a heavier machine when the work earns it — not one fixed machine for everyone.
One filesystem, many hosts
03 · Control
Consequences stop with you.
Sending, publishing, buying, deleting, and changing permissions pause at an approval boundary you can inspect.
An approval boundary
04 · Continuity
Work can outlast the open laptop.
A routine wakes a named teammate on a schedule or event — the computer only spins up when the work actually needs it.
Wakes on a schedule
A channel is the room.
Every teammate in a channel reads the same compacted view. Only the teammate you address acts. Handoffs happen in the work instead of turning you into the router between agents.
Control is the product
Any model can talk. What’s missing is discipline: who did what, on whose authority, and what happens when it’s wrong. Chatticus gives the organization rules for method, timing, quality, and consequence.
Four controls.None of them are chat.
02
Routine
Wake it when it matters.
A routine gives one teammate a schedule or event trigger, a time zone, and a clear no-data policy.
Scheduled or event-driven03
Review
Evidence travels with the work.
Reviewers can inspect results, tests, and provenance before the task moves forward or returns for repair.
Quality before motion04
Approval
A proposal waits for a person.
Consequential actions pause before they happen. Approval controls the proposed action; it never pretends to undo completed work.
Human consequence boundaryWorked examples
Three organizations built out of named desks. Every bot is named for the job it does, so the roster reads like an org chart and nobody has to remember which teammate was which.
Who would sitat the desks?
Nimbus Cloud Systems
Software factory
Four product teams, one release train
- Software Director
- App Product Owner
- Web Product Owner
Harbor Lantern Media
Automated newsroom
Steered by editors, operated by desks
- Assignment Desk
- Wire Desk
- Reporting Desk
Ridgeline Supply Co.
Back office
The unglamorous work, done on time
- Payables
- Receivables
- Payroll
Control and access
Control without lock-in. Access without a queue.
Your Chatticus organization runs in an AWS account you own, on your network, under your logging. We access it via a cross-account CloudFormation template and scoped IAM policy.
The code is MIT licensed. Free to copy, change, and run. Run your bot farm on our infrastructure, or take the whole stack and run it yourself.
Control on its own can read as more work for you, so here’s the other half. Anthus runs its own organizations on Chatticus, and buying the managed service puts you next to them: managed customers run what Anthus runs, which gets you the developers instead of a support queue.
Get migration helpGH
Already in your account
Your file system and encrypted secrets live in your AWS account from the start — not something trapped behind an API only we control.
Open the repositoryAWS
Take it to another host
The same infrastructure-as-code that runs Chatticus for you can stand up your bot farm on any cloud account — yours, ours, or someone else's.
Read the infrastructureBDD
No hidden rules
Every approval, escalation, and recovery rule is a written, testable specification — not tribal knowledge you'd lose by switching providers.
Read the specificationsHow it fits together
Who works here. Where they work. Who decides.
Chatticus is one system with three moving parts: a roster that stays named, a computer they all share, and a line that consequential work has to stop at.
Teammates
- Durable named bot records and memory
- Household tasks and turn journals
- Role and reporting-line controls
- Turn-scoped progress over server-sent events
The computer
- Computerless turns that escalate on first computer use
- One shared computer start across concurrent turns
- Durable handoff and recovery across worker failure
- A computer preview and work history
Control
- Policy checks at consequential system sinks
- Approval cards and human takeover in the product app
- A complete skills and routines authoring surface
- Development, staging, and production boundaries
The thinking behind Chatticus
Why organization, ownership, and attention matter more than one more model benchmark.
Delegated responsibility
You can run the whole stack yourself. If you want help, we can operate it, set it up with you, or adapt a deployment to what you need.
You choose how much we help
Fork it
MIT licensed. Deploy it yourself. Anthus does nothing and charges nothing.
No cost
Self-setup, managed
You run the CloudFormation template in your account; we operate it and keep the deployment updated. We update our own organizations first.
$20 a month
Assisted setup, managed
We run the setup session with you, then operate it. We keep the deployment updated, updating our own organizations first.
$20 a monthand $100 once
Professional services
We adapt a deployment to your exact needs, with or without the managed service.
Quoted
Straight answers
Before you hand over a task.
Chatticus teammates share the same files — there’s no always-on socket and no separate machine per bot.
Chatticus
Give people and botsa room of their own.
Sign in to the workspace as it stands today, join the beta, or read the source and tell us where we’ve got it wrong.
Open sourceYour infrastructureHuman approval boundariesNo invented metrics