CellCog

Managed AI employees with persistent inboxes and boards, scheduled shifts, and user-configured signoff rules.

No product visual on file

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.

How we classify it

Unattended scheduler/heartbeat with write-tools; failure has a real owner.

Runs unattended

Yes — that capability is documented in this brief.

Trigger

The employee launch documents owner-set schedules and wakes from inbound email, a due task or a user message. These are employee capabilities, not a claim about every SDK call.

State

Employee email threads, task boards and memory persist across working sessions; the employee writes a handover for the next session.

Tools

The launch describes sending/receiving real email and producing code, dashboards, spreadsheets, PDFs and media. Connected-system actions depend on granted permissions and separately configured signoff.

Human control

Actions marked for signoff wait in the waiting-on-you lane; users can redirect the employee and supply feedback. A human/organization remains accountable for monitoring and incidents. Assign that owner to review waiting work and failures; retry/recovery and concurrency policies are setup requirements to verify, not guaranteed automated controls.

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.

Where it runs

cloud

Data boundary

Not recorded yet.

Identity & permissions

Not recorded yet.

What it can write

role task boards · email and connected work under granted permissions · handover notes and deliverable files

Surfaces

Hosted chat · employee email inbox · task board and channels · scheduled shifts

Export / lock-in

Not recorded yet.

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.

Evidence status

documented

Source set

5 primary sources

Evidence review

2026-10-14

Sources on file

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.

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.