Operational brief
CellCog
Managed AI employees with persistent inboxes and boards, scheduled shifts, and user-configured signoff rules.
Choose it when
You want a hosted agent to hold a standing role, retain work across shifts, and return decisions for approval rather than wait for the next prompt.
Skip it when
You need a local runtime, a conventional prompt-by-prompt assistant, or independently validated operational performance before deployment.
01 / Classification
Autonomy evidence
This is our classification, not a vendor badge. The record says what the product normally does. The gaps stay visible.
02 / Operations
Control reality
Useful agents eventually touch something real. This is the operational picture we have, not a promise hidden in a sales page.
03 / Receipts
Evidence ledger
Here is what this brief is built on. “Documented” means we found a source. “Tested” means this desk actually ran it. Those are different things.
Sources on file
- https://cellcog.ai/ai-employees
- https://cellcog.ai/blog/meet-your-ai-employee/
- https://cellcog.ai/for-agents
- https://cellcog.ai/blog/ai-employee-permissions-and-approvals/
- https://cellcog.ai/blog/ai-employee-shifts-and-schedules/
- https://cellcog.ai/support/approvals-and-safety-guide
- Homepage · https://cellcog.ai/ai-employees
Corrections
- 2026-10-14 · Replaced universal dangerous-action approval wording with user-configured signoff. Added the employee schedule/state/write/owner bundle, qualified free hire/trial versus usage-based work, and removed the unsupported employee Python SDK surface. Retained June 21 launch: the September 29 article update isn't a newer product release.
- 2026-11-17 · Corrected exclusive signoff wording: CellCog describes a shared approval level, not unified technical access grants. Above-level employee work can use an active standing approval; authorized recent chat instructions or yes can also approve a dangerous step without a second card. Owner, shared Team members and enabled managers have specified rights; if the person cannot approve, the step doesn't run and the owner gets a task. Otherwise active-user pending approval has a 15-minute no-decision timeout and away behavior fails immediately with guidance. Standing grants can have scope and expiry; documented existence, activity and expiry checks are distinct from wording and limits the employee is expected to honor. Outgoing employee email has a separate dangerous-operation policy and no approval button. Risk classification, defaults and actual enforcement remain unverified; no desk test or security guarantee.
04 / Change log
Related coverage
The brief tells you what the product is. Payloads track the changes that may alter the decision.
No linked change coverage on file yet.