Skip to content

GitDocket v0.3.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 13 Sep 02:22
· 30 commits to main since this release
v0.3.0
650467a

GitDocket 0.3.0

GitDocket 0.3.0 adds saved project guidance, a shared browser editor, and a simpler path from one useful task to a fresh agent session that can use what the project learned.

Saved project guidance

  • Save standards and scoped procedures in ordinary linked Markdown, then ask your agent to inspect, revise or retire them.
  • Use the new Project guidance destination to manage instructions and procedure links through the browser. Removing a guidance link preserves the shared source document.
  • Make relevant guidance discoverable before direct or tracked implementation through repository instructions, native adapter files, task context, and the new project_guidance MCP tool or docket guidance command.
  • Preserve project-owned guidance and local instructions through initialization and upgrades.

Guidance is optional. Saving a procedure does not authorize its execution, and saving an instruction does not guarantee that an already-running agent has read or applied it. Agents are instructed to reread after explicit changes or before the next piece of work. Controlled fresh-session checks demonstrated saved rules applied to implementation; native client and authentication limits remain documented.

Edit authored documents in the browser

  • Edit titles, descriptions and complete Markdown bodies across tasks, epics, specs, references, playbooks, decisions, workflows and custom concepts with one shared editor.
  • Preview changes, save explicitly, and recover same-tab drafts after navigation or reload where browser storage is available.
  • Detect changed source versions, retain the draft, and review and reconcile the latest source before retrying.
  • Distinguish local saves, optional successful commits, and source saved with a failed commit. Unrelated staged work remains intact.

Generic content edits preserve IDs, lifecycle state, provenance and evidence fields. Editing an acceptance checkbox does not complete a task. Generated views and reserved introduction, briefing and log sources retain their existing workflows. Draft recovery is best-effort; closing the tab or losing storage can lose a draft. Complete-source editing supports Markdown files up to 256 KiB, with documented limits for arbitrary external writers.

Start smaller and carry knowledge forward

  • Begin with one standalone task; specs, epics, a populated wiki and saved guidance are optional.
  • Follow the revised homepage, one-task tutorial and everyday-use guide to inspect what changed, why, and what was checked.
  • See a retained demonstration where a separate fresh agent uses a task-recorded decision and a browser-edited convention to plan later work.
  • Get clearer recovery instructions for missing or stale briefings, local-save explanations, and completion/follow-up guidance.
  • Open and share tasks and epics through stable ticket-number URLs that survive title changes.

The demonstration distinguishes scripted work from controlled agent execution. Agent-proxy comprehension checks are not human customer research, and a completed status alone does not establish correctness.

Upgrade

Requires Bun 1.3.14 or newer on macOS or Linux:

bun add --global @gitdocket/cli@0.3.0 @gitdocket/mcp@0.3.0
docket --version

Restart Serve processes and reconnect MCP clients. In each existing project, run docket upgrade, review local workflow customizations or conflicts, then run docket index and docket lint. The workflow ledger preserves the exact published 0.2.1 and 0.1.1 bodies as upgrade merge bases; 0.3.0 carries the new guidance and planning workflows. No project-document migration is required.

All four packages (core, web, cli, and mcp) use version 0.3.0. Telemetry remains opt-in and local. Existing large-project performance qualification and usage pilots remain open; this release adds no latency or memory SLA.

Verification

Assets 3
Loading