Project memory, checked into Git

Give your agent the whole project.

GitDocket keeps context, decisions, work, and operating rules in one linked Markdown graph—so humans and coding agents can pick up where the project actually is.

Install the preview View on GitHub

Local-first
Plain Markdown
Reviewed through Git

GitDocket Home for the synthetic Harbor project, summarizing recent progress, the next task, and an important product decision — Return to a project and see what changed, what matters, and what is ready next.

Less reconstruction.

Clearer delegation.

Durable decisions.

See the project, not another dashboard

One source of truth. Several useful views.

The interface stays thin because the repository already holds the facts. Each view answers a concrete question.

Track the work

See flow, priority, and blockers at a glance.

The board is a live view of Markdown tasks. Status changes follow the same rules whether a human or an agent makes them.

GitDocket board for the Harbor public beta, with tasks organized into todo, in-progress, blocked, review, and done columns — Ready work stays distinct from active work and honest blockers.

Know what finished means

Keep context, criteria, and proof together.

A task carries its dependency state, acceptance criteria, working log, and linked Git activity.

A GitDocket task showing status, priority, dependency, context, checked acceptance criteria, log, and a linked commit — The work item and the evidence that completes it stay connected.

Follow the why

Decisions remain readable in context.

Specs, decisions, tasks, and reference docs form one navigable graph instead of drifting across tools.

A GitDocket decision page showing its context, accepted decision, consequences, and nearby project documentation — The rationale remains beside the work that depends on it.

A small operating layer

Files hold memory. The engine keeps facts honest.

01
Link the project

Plans, specs, decisions, tasks, and epics stay readable Markdown.
02
Derive the state

Readiness, transitions, indexes, and activity come from deterministic commands.
03
Run the outcome

Checked-in workflows guide agents through pickup, verification, and closure.
04
Keep the receipt

Commits link implementation to the task and its reconciled documentation.

Ask for the outcome

The project carries its operating rules.

Run the launch epic.

Supervise ready work, verify each result, and stop on one concrete blocker.

Groom the backlog.

Find stale tasks and broken dependencies before reprioritizing anything.

Check the docs for drift.

Review recent commits against the project knowledge they may have changed.

Practical trust

Inspectable by design.

No second database

Markdown and Git remain authoritative. The cache is disposable.

No hidden policy

Agent procedures live in the repository for the team to review.

No fake certainty

Facts come from the engine. Judgment and blockers stay explicit.

Public preview

Make the next handoff easier.

Start with the repository you already have. Initialization is additive and leaves existing Markdown untouched until you review it.

Install from source Read the quickstart