An open-source workspace for agent-driven work
Taskrivet brings terminal sessions, coding tools, context, and failure records into one desktop workspace. Explore how the pieces fit together—and where the system still needs human judgment.
Guide to v0.3.0 · Published October 21, 2026 · Implemented behavior and planned capabilities are identified separately.
01 / The architecture
The ticket source owns the work. Taskrivet keeps sessions and evidence together. GitHub activity enters as information to evaluate.
The embedded viewer is the released, hash-verified artifact. Typed diagram source · Validation and visual-review receipt
02 / Execution, recovery, completion
Follow the implemented local task states, the routes back to Ready, and the separate decision that accepts a result.
Typed lifecycle source · Validation and visual-review receipt · Implementation used for this map
A recorded failure, expired lease, exhausted reported budget, or three identical checkpoint evidence entries blocks ledger progress. The operator reconciles the worker and records a reason before retry. Retry returns the task to Ready; it preserves failure history and cumulative reported usage. Starting again still checks the remaining budget and resource ownership.
The intended executor will classify the blocker, use bounded recovery attempts, change tools or approach when justified, and work on another eligible ticket when progress is unavailable. Scoped authority, verification, and source-owned acceptance must be enforced before this becomes autonomous behavior.
This is the local ledger lifecycle, not proof of external ticket completion. Finish requires a checkpoint and evidence; an explicit acceptance decision is separate. Cancellation is also supported from Ready, Blocked, and Review—the map shows the latter two paths. A blocked or cancelled ledger record does not itself terminate a process.
03 / Follow the work
Select a step to see its purpose, current behavior, and execution boundary.
The optional ticket preview reads a bounded page from an explicitly configured local ticket service. It shows source state, readiness, and known holds. Taskrivet also has its own local coordination ledger.
Reading a ticket does not claim it or authorize execution. Automatic ticket selection and atomic source claims remain planned.
04 / Connections with boundaries
Observe issues, comments, pull requests, review comments, commits, workflow runs, releases, and repository events. Deduplicate repeated observations and retain changed revisions.
A private adapter can write a repository activity digest into an explicitly mapped existing ticket. Revision checks and independent readback preserve source ownership and expose conflicts.
An outbox binds a selected public summary to an issue and publication key. It checks the author and exact content, verifies delivery, and avoids blind retries after an uncertain send.
Polling is bounded and can miss activity. Suggested response categories guide review; they do not automatically execute contributions, merge changes, create tickets, or mark work Done. Full per-issue lifecycle synchronization and webhook delivery remain planned.
05 / A truthful status
06 / Inspect the evidence
Validation results describe this release. They do not establish universal coverage or autonomous completion.
Python checks run on Linux and macOS, alongside desktop tests and packaging. Open the exact run and revision for its results; a past release count is not current validation.
Zero validation errors or warnings. Browser containment and manual visual review are recorded separately from deterministic validation.
Mac arm64 application, Python distributions, checksums, and a separate CLI container. The desktop alpha requires Python 3.11+ and is unsigned.
07 / The workspace
Each pane keeps its session, task, context, and evidence in view. These captures render the real workspace interface with synthetic data.
Captures come from the workspace renderer driven by a synthetic bridge. They show the interface, not a live run, and the values shown are records rather than measured facts.
08 / Build with us
The focused roadmap tracks qualified ticket execution. Existing planning entries need scope and acceptance review before they become implementation work.