Skip to main content

cohors

A governed control plane for all your git repositories: for you, and your coding agent.

Coding agents made single-repo work cheap. The bottleneck moved to the fleet: an agent is blind across your 20 repos, and so are you past cd-ing through a dozen terminal tabs. cohors is one fast view of every repo, a search that indexes the whole fleet, and bulk actions an agent can preview before you ever grant write access. In the terminal, in the browser, and over MCP. One Rust core.

Install

pip install cohors   # prebuilt binary, no Rust toolchain
cohors               # auto-detects your repos and launches the dashboard

With no config, cohors scans every folder it finds git repos in (your "super fleet"). Point it at a single folder with cohors --root ~/code, or run cohors init to save an editable config.

pip install cohors bundles a prebuilt binary for macOS (Apple Silicon / Intel) and Linux (x86_64 / ARM64). On other platforms, build from source: cargo install cohors.

What you get

  • Dashboard (cohors): every repo on one screen (branch, ahead/behind, dirty state, stashes, CI, open PRs), sorted by what needs you. Bulk fetch / pull / run a command across the ones you pick, with a dry-run preview first.
  • Browser (cohors web): the same scan, in your browser. Try it instantly with cohors web --demo.
  • MCP server (cohors mcp): gives your coding agent (Claude Code, Cursor, ...) the same fleet-wide sight. Read-only by default; every write is gated and previewable, so it can't fan out across your machine on a fumbled command.

One core powers all three, so the terminal, the browser, and your agent always agree.

Full docs, the web dashboard, and MCP setup: https://github.com/rushirb2001/cohors

MIT licensed.

mcp-name: io.github.rushirb2001/cohors

Metadata

Release files for cohors 0.7.5

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

Built distributions (wheels)

Table of built distributions (wheels) for cohors 0.7.5
File Actions
cohors-0.7.5-py3-none-manylinux_2_35_x86_64.whl Python 3 none Linux glibc 2.35+ x86-64 Details for cohors-0.7.5-py3-none-manylinux_2_35_x86_64.whl
cohors-0.7.5-py3-none-manylinux_2_35_aarch64.whl Python 3 none Linux glibc 2.35+ ARM64 Details for cohors-0.7.5-py3-none-manylinux_2_35_aarch64.whl
cohors-0.7.5-py3-none-macosx_11_0_arm64.whl Python 3 none macOS 11.0+ ARM64 Details for cohors-0.7.5-py3-none-macosx_11_0_arm64.whl
cohors-0.7.5-py3-none-macosx_10_12_x86_64.whl Python 3 none macOS 10.12+ x86-64 Details for cohors-0.7.5-py3-none-macosx_10_12_x86_64.whl

Total release size: 20.3 MB

Release files / cohors-0.7.5-py3-none-manylinux_2_35_x86_64.whl

Download URL cohors-0.7.5-py3-none-manylinux_2_35_x86_64.whl
Size 5.3 MB
Tags Linux glibc 2.35+ x86-64 Python 3
SHA-256 checksum
How to use checksums
52fafc0af82aaa034f187130c0225cefc8b12c53088f296d7133f4eebf9ca496
BLAKE2b-256 checksum
How to use checksums
41214c0933fa55b1abda8dfcb25186c2342a95a437f1c8459a8ee92f0961b9f4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / cohors-0.7.5-py3-none-manylinux_2_35_aarch64.whl

Download URL cohors-0.7.5-py3-none-manylinux_2_35_aarch64.whl
Size 5.0 MB
Tags Linux glibc 2.35+ ARM64 Python 3
SHA-256 checksum
How to use checksums
2552ee3b9a481f4851b21df4d35ec49360af39e664cea27453a278969c636f03
BLAKE2b-256 checksum
How to use checksums
bb0bb0d34e93809734801bdce569978feb0ce425d8efb960d1cfd4ca47f46b63
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / cohors-0.7.5-py3-none-macosx_11_0_arm64.whl

Download URL cohors-0.7.5-py3-none-macosx_11_0_arm64.whl
Size 4.8 MB
Tags Python 3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
04d6ee594407973768184cb68ea0fbda9954e558cc3c555ce0c8b2bad7ae3287
BLAKE2b-256 checksum
How to use checksums
879e2fe869ce44aad4e6c0a149171191971ccc2ffeb12ac6fbe24547b172c5a7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / cohors-0.7.5-py3-none-macosx_10_12_x86_64.whl

Download URL cohors-0.7.5-py3-none-macosx_10_12_x86_64.whl
Size 5.1 MB
Tags Python 3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
61bd628c84a1991f506f0d9d32c5f9206f5139e3f763ae3a750ee9ed63f78399
BLAKE2b-256 checksum
How to use checksums
ae3abf30d697acd9ca7cc34f6e59d850e6a36d0a9039f6f7324cf88077e3ea9b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Security for cohors 0.7.5

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 4 files in this release have been uploaded with provenance metadata.

Select from 4 files

Attestation for cohors-0.7.5-py3-none-manylinux_2_35_x86_64.whl

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 Nov 12, 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.

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