Skip to main content

Dock

Local inbox and claim evidence for coding agents. Developers still merge. Dock checks whether the agent told the truth.

It is not a model. It does not review architecture. It does not run your tests. It scores PR prose against git/GitHub facts (changed paths + patch) with fail-closed checkers. Unknown is the point: a human still looks.

Works on any git repo. Cursor, Claude Code, Copilot, Codex, and the rest are all just git + GitHub.

The product and CLI are Dock. The install name is dock-inbox (dock on PyPI is a chemistry toolkit).

pip install dock-inbox
dock inbox --path /path/to/any/repo
dock merge --pr 12          # preview + GitHub merge button — does not merge

Until the first PyPI release, this also works:

pip install "git+https://github.com/mobigaurav/dock.git"

Copy examples/github-inbox.yml to .github/workflows/dock.yml so every PR gets a pass/fail/unknown comment.

Python 3.11+, git, and GitHub CLI (gh) for pull requests.

make test
dock inbox --path .

What a “pass” means

Claim shape When it can pass
Names a file That path is in the diff
Mentions tests (in Summary, not a Test plan command) A test path is in the diff
Mentions README/docs and a URL That URL appears in the patch
Mentions README/docs with no URL unknown — a changed README is not enough
Test plan npx jest foo.test.ts ignored — files existing is not tests passing
Anything else unknown

Pass is not an approve. Dock will not merge until a person clicks Merge on GitHub.

Install in Cursor

pip install dock-inbox
ln -s /path/to/dock/.cursor/skills/dock ~/.cursor/skills/dock

Say what needs me or dock inbox.

Claude Desktop / Claude Code

{
  "mcpServers": {
    "dock": {
      "command": "dock",
      "args": ["mcp"]
    }
  }
}

MCP tools: dock_inbox, dock_merge_preview. There is no merge tool.

Merge

dock merge --pr N never merges. It prints claim cards and the GitHub Merge URL.

dock merge --pr N --execute only works in an interactive terminal after you type MERGE #N.

Optional shortcuts

Copy dogfood.example.json to dogfood.local.json (gitignored) if you want --target aliases. Otherwise use --path.

Metadata

Release files for dock-inbox 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dock-inbox 0.1.0
File Size Uploaded Provenance Actions
dock_inbox-0.1.0.tar.gz 19.0 kB With provenance Details for dock_inbox-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for dock-inbox 0.1.0
File Interpreter ABI Platform Actions
dock_inbox-0.1.0-py3-none-any.whl Python 3 none any Details for dock_inbox-0.1.0-py3-none-any.whl

Total release size: 38.3 kB

Release files / dock_inbox-0.1.0.tar.gz

Download URL dock_inbox-0.1.0.tar.gz
Size 19.0 kB
Tags Source
SHA-256 checksum
How to use checksums
1624678e012dad72769c0c98d615b18bc2d69fa1e7453ad93313c10c0ded2e64
BLAKE2b-256 checksum
How to use checksums
6900f7a77787685f6082bce326226e0996183d804ddeb8792b7e0a4179402832
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.

Transparency log

Release files / dock_inbox-0.1.0-py3-none-any.whl

Download URL dock_inbox-0.1.0-py3-none-any.whl
Size 19.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
44a2ca598fb72019085fd7f5251c03c5890509931a2954d2167301b83e5fc237
BLAKE2b-256 checksum
How to use checksums
65ed3a7d1e924c703d1bb1009cfce80d00d5503d020cc05c82625cd6918e41f7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.

Transparency log

Security for dock-inbox 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for dock_inbox-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page