A local TUI and workflow harness for Cursor agent teams: see which local agents and worktrees are doing what, from passive hooks and read-only git, without sending anything anywhere.
Unofficial: CursorFleet is not affiliated with or endorsed by Anysphere or Cursor. "Cursor" is a trademark of its respective owner.
Status
Pre-alpha. v0.1.0 is on
PyPI and
GitHub Releases. Latest on PyPI: 0.1.1; main may be ahead.
- v0.1 is Observe: no enforcement, no forced approvals, and no cloud-agent visibility (local Cursor sessions only). It is not a security boundary: a malicious or prompt-injected agent can bypass or forge what it shows (threat model).
- Live Cursor (product hooks): maintainer smoke on Linux Cursor IDE 3.22.7 confirmed hook
telemetry, subagent lifecycle, and artifact scanning; see
live validation index. Q1/Q2 (subagent identity
on tool hooks, custom
subagent_typenaming) remain OPEN; M0a formal matrix is not complete. - M2.5 active: task-centric observer work (Active Run) is in progress; see status. The M0a capture kit (spike) remains separate.
- Supported surface for claims today: local Cursor IDE (desktop) on Linux for the exercised smoke only; CLI, Agents Window, worktrees, and parallel subagents are not claimed until matrix PASS. The Cursor CLI, the Agents Window, Cursor-managed and manual worktrees, parallel subagents and cloud agents are not claimed.
- The name "CursorFleet" is a working name; the final name is a release gate (ADR 0005).
- Linux is the tested platform; macOS and Windows are CI-tested only (platform support).
- Cursor is the only officially supported IDE; internals are adapter-ready but no other adapter is planned for v0.1.
- Local only: no network calls, no telemetry, no accounts (checked by a test). It never stores prompts, model thinking, responses, file contents, command output, environment variables, emails or transcript paths (privacy).
Install
Needs Python 3.11+ and git.
uv tool install cursorfleet # or: pipx install cursorfleet
cursorfleet --version
From a git checkout (contributors or unreleased main):
git clone https://github.com/M9nx/cursorfleet && cd cursorfleet
uv tool install .
See the installation guide on the docs site and the release checklist.
Optional container (shows under GitHub Packages; install with pip for normal use):
docker run --rm ghcr.io/m9nx/cursorfleet:0.1.0 --help
Quickstart
# from the repository root (Git is required; no --allow-non-git)
cursorfleet init --cursor --dry-run # review the exact diff first
cursorfleet init --cursor # install the observe-only hooks and kit (once per repo)
# ...work with Cursor agents as usual...
cursorfleet doctor # check hooks, runtime dir and spool
cursorfleet tui # open the dashboard (needs an interactive terminal)
cursorfleet status --json # stable machine-readable snapshot for scripts
cursorfleet uninstall # remove exactly what init added
Full walkthrough: Quickstart on the docs site
(in-repo: docs/quickstart.md). No Cursor handy? Run the
synthetic demo (scripts/demo.sh).
Dashboard keys: o overview, l timeline, w worktrees, g gates, e evidence, v
violations (v0.2 placeholder), / filter, p pin, t tiles (160+ columns), r re-read,
? help, q quit. The TUI only observes: silence shows as STALE / OFFLINE, never idle, and
gate tiles are heuristic and non-authoritative, not proof that anything passed. Details:
docs/tui.md.
Documentation
Docs site (GitHub Pages) — start with Getting started.
In-repo: Quickstart · governance model ·
demo · kit reference · TUI ·
status --json · product contract ·
architecture · privacy ·
threat model · security review ·
platform support · hook latency ·
release checklist · project status ·
empirical test plan · follow-ups ·
docs-site plan · ADRs ·
changelog
Development
uv sync --all-extras
uv run cursorfleet --version
uv run ruff check . && uv run ruff format --check . && uv run mypy src && uv run pytest
Regenerate schemas with uv run python scripts/gen_schemas.py. See
CONTRIBUTING.md, AGENTS.md and SECURITY.md.
License
MIT, see LICENSE.
Metadata
Release files for cursorfleet 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cursorfleet-0.1.1.tar.gz | 783.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cursorfleet-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 980.8 kB
Release files / cursorfleet-0.1.1.tar.gz
| Download URL | cursorfleet-0.1.1.tar.gz |
|---|---|
| Size | 783.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f7bad15954a3aee488e23e282d8ff4cb5795a092d2e53dbfe3d446ca26658955
|
|
BLAKE2b-256 checksum How to use checksums |
7da20b5296593b06f1a6f2dd8f7d4d76ed1632dc3fc3cbfe5947fdd9f97477c0
|
| 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 Oct 12, 2026.
Transparency logRelease files / cursorfleet-0.1.1-py3-none-any.whl
| Download URL | cursorfleet-0.1.1-py3-none-any.whl |
|---|---|
| Size | 197.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
035e2cb072b1d366dee1076ef6adfd3717e66e20d84ff3b3e9e37101131803e8
|
|
BLAKE2b-256 checksum How to use checksums |
bd844b732a63841ede94d75691e0f426acc9527b59eeb43c26723632275754ef
|
| 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 Oct 12, 2026.
Transparency logSecurity for cursorfleet 0.1.1
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for cursorfleet-0.1.1.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 Oct 12, 2026.
Transparency logA 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.