What does a task manager look like when agents are first-class users?

Hypothesis

Every task tool assumes a human is the only actor. If agents are going to do real work, the task manager needs them as first-class citizens: agents that own tasks, agent runs as records, and full lineage of who (or what) did what.

What we built

Bloom: a project/task manager in the familiar board-and-list shape, but with an agent layer underneath — an actors model where every change is stamped human or agent, agent-run records, and a lineage graph of how work items came to be. It's wired into the AI OS: speak a task into the voice assistant and it lands on the board via the kernel; agents pick work up and their activity is auditable per card.

Learnings

• The schema change that matters is tiny: an actor on every write. Once provenance is first-class, trust in a mixed human/agent workspace follows.
• Voice → kernel → board is the pipeline that makes a task manager actually get used — capture has to be faster than forgetting.
• The server's database must be the single authority. The moment two copies of "the board" exist, agents and humans diverge instantly.

Log

• 2026-07-10 — Running on our server as a service; voice-to-task pipeline fixed end-to-end.
• 2026-07-01 — Core board, actors model, and lineage built.