Repository navigation
GitDocket v0.2.1
GitDocket 0.2.1
GitDocket 0.2.1 brings faster repeated reads, a redesigned local workspace, opt-in local telemetry, and a shorter website with focused reference docs.
Faster project navigation and agent reads
- Reuses parsed concepts, exact search indexes, Serve snapshots, and Git evidence across repeated reads instead of repeatedly rebuilding the project.
- Adds bounded pages for browser collections and source/history retrieval, while preserving complete CLI/MCP exports when requested.
- Keeps persistent MCP reads warm and coordinates task writes across processes.
- Adds the
source_pageMCP tool anddocket sourcecommand for bounded Markdown reads with source hashes and continuation cursors.
These changes improve ordinary browsing and agent workflows. Cold starts, large exports, and very large project memory costs still need further qualification; this release does not promise a latency or memory SLA.
A clearer local workspace
- Makes Home and Board the first navigation destinations, with a compact board overview and project re-entry context on Home.
- Adds a document-focused Wiki workspace and clearer reading, metadata, navigation, and pagination across work views.
- Improves board controls, filtering, collapsed empty columns, epic editing, and responsive layouts while keeping Markdown and Git authoritative.
Local telemetry, explicitly opt-in
Telemetry is off by default and enabled separately for each checkout:
docket telemetry enable
docket telemetry status
docket telemetry reportObservations stay on the local computer, outside the repository. Docket never uploads them. The allowlisted records cover operation counts, timings, errors, and sampled runtime memory; they exclude document contents, prompts, search terms, task IDs, and file paths. Reports show sample and coverage limits.
Use docket telemetry disable to stop collection and docket telemetry delete to remove the current checkout's enrollment and retained observations. Exports you create remain yours to manage.
Website and reference
The homepage is shorter and shows the current interface. On-site docs cover setup, CLI commands, MCP workflows and input schemas, and a small reference for the local browser API. The scripted Harbor example retains inspectable CLI evidence and replay instructions.
Release validation
This release also fixes a macOS-specific test temporary path and aligns the macOS/Linux CI toolchain with the publication workflow. The earlier v0.2.0 tag stopped at preflight before publishing packages; 0.2.1 supersedes that candidate.
Upgrade
Requires Bun 1.3.14 or newer on macOS or Linux:
bun add --global @gitdocket/cli@0.2.1 @gitdocket/mcp@0.2.1
docket --versionRestart running Serve processes and reconnect MCP clients to load the new code. In each existing project, run docket upgrade, review any local workflow customizations or conflicts, then run docket index and docket lint. The released 0.1.1 workflow bodies remain the upgrade merge base.
All four packages (core, web, cli, and mcp) use version 0.2.1. Telemetry remains disabled until explicitly enabled for that checkout.
Verification
- Publication receipt: attached
registry.json(SHA-256adbda1ac760717df404af523a4e0d3583b35dbeec4839e7871bc94ef2f7e6acb) - npm trusted-publisher provenance:
- @gitdocket/core@0.2.1
- @gitdocket/web@0.2.1
- @gitdocket/cli@0.2.1
- @gitdocket/mcp@0.2.1