One identity, more than one possible host
A computer is a workplace, not a machine.
The workplace identity is what's durable. It can run on a scale-to-zero container today or on hardware you already own — same files, same sessions, either way.
Not one fixed machine for everyone
The files are shared.The compute isn’t fixed.
Some systems give every bot the same single computer with a different view onto it. Chatticus keeps the files constant — one shared filing cabinet every bot reads and writes — and lets the compute underneath vary: a light container for most work, something heavier for work that actually needs it, picked per task instead of fixed for the whole team.
How it works
Async work gets its own short-lived container
Background work doesn't sit on a dedicated machine.
A routine or background task summons a container just for that job, does the work, publishes the result, and exits — nothing idles per bot waiting for the next task.
Heavier work, when it's actually heavier
The container fits the task, not the other way around.
Most work runs light. Work that genuinely needs more — a bigger instance, a full desktop — is meant to ask for that by name, not force every task onto the same fixed shape.
How the computer is shaped
One identity, whatever host the work needs
An identity, not a machine
A computer is a workplace identity, not one fixed machine — it runs on a scale-to-zero container, or on hardware you already own, with the same durable files either way.
A container per job
Background work summons its own short-lived container, does the job, and publishes — no dedicated machine sits around per bot waiting for the next task.
Host shapes on request
Bigger instances and full desktop sessions are host shapes a task asks for by name, chosen automatically for the work instead of configured by hand.