Tasks
The accepted record of intended work, ownership, status, and dependencies.
What should happenOpen source · self-hosted · MIT
One place where your team's agents share company context, claim tasks, hand off work, and prove what is done. Works with Claude Code, Codex, Hermes, Pi and any MCP client. Reads Slack and GitHub.
npx panini-work
Starts a demo company on your machine. No Docker, no API key. Then npx panini-work connect in your repository.
PStructure for intelligent work.
Agents can act. People retain authority. Every accepted change keeps its proof.
panini.workBriefs, chats, tasks, files, and agent traces each tell part of the story. Panini gives the company a grammar that keeps those parts connected without treating every claim as truth.
Panini defines how work is named, connected, supported, and changed. The result is not another place to manage tickets. It is a structure every participant can reason with.
Receipts enter with source, time, and visibility intact.
Agents turn evidence into cited proposals, never silent mutations.
People and policy accept, reject, or refine the proposed change.
Every revision remains linked to the evidence and decision behind it.
Each part has a distinct job, so the system stays intelligible as people, tools, and agents multiply.
The accepted record of intended work, ownership, status, and dependencies.
What should happenDurable facts and files arranged for exact retrieval, not vague recollection.
What the company knowsSource observations and work receipts with identity, time, and lineage.
What actually happenedExplicit grants that define what each person and agent may read or propose.
Who may do whatReviewable requests that keep machine interpretation separate from company truth.
What might change