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). On other platforms, build from source: cargo install --git https://github.com/rushirb2001/cohors cohors-tui.
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 withcohors 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.
Links
Full docs, the web dashboard, and MCP setup: https://github.com/rushirb2001/cohors
MIT licensed.
1 maintainer
Metadata
1 maintainer
Release files for cohors 0.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cohors-0.6.0-py3-none-manylinux_2_31_x86_64.whl | Python 3 | none | Linux glibc 2.31+ x86-64 | Details for cohors-0.6.0-py3-none-manylinux_2_31_x86_64.whl |
| cohors-0.6.0-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details for cohors-0.6.0-py3-none-macosx_11_0_arm64.whl |
| cohors-0.6.0-py3-none-macosx_10_12_x86_64.whl | Python 3 | none | macOS 10.12+ x86-64 | Details for cohors-0.6.0-py3-none-macosx_10_12_x86_64.whl |
Total release size: 12.3 MB
Release files / cohors-0.6.0-py3-none-manylinux_2_31_x86_64.whl
| Download URL | cohors-0.6.0-py3-none-manylinux_2_31_x86_64.whl |
|---|---|
| Size | 4.4 MB |
| Tags | Linux glibc 2.31+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
7d166181ed6c8b387b13cfbd1f5cc2331bd7fd0f19c55a9736e1cb40fc784d5c
|
|
BLAKE2b-256 checksum How to use checksums |
90a5da37b7e38d83d2ef4afd2c1f33dab37c8a6875145b813add74afb936e4ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 23, 2026.
Transparency logRelease files / cohors-0.6.0-py3-none-macosx_11_0_arm64.whl
| Download URL | cohors-0.6.0-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.8 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
82c1bac38cd1abfda6e2580972de4bc1c2157a236ff76573a12d35b9f5477d80
|
|
BLAKE2b-256 checksum How to use checksums |
f2e77e932c739d78f48ca4318ee1bc5465307cf7bd0619a81398170c82f314f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 23, 2026.
Transparency logRelease files / cohors-0.6.0-py3-none-macosx_10_12_x86_64.whl
| Download URL | cohors-0.6.0-py3-none-macosx_10_12_x86_64.whl |
|---|---|
| Size | 4.1 MB |
| Tags | Python 3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
a72d310eece3f526f490a9ba2d091603e900cdb0b7fd7dd03c9711d5ead7a148
|
|
BLAKE2b-256 checksum How to use checksums |
0069c94d4aaff1290eff2d39800b8eef6dd711cdc4cb76c38cec5c99bb71c134
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 23, 2026.
Transparency logSecurity for cohors 0.6.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
All 3 files in this release have been uploaded with provenance metadata.
Attestation for cohors-0.6.0-py3-none-manylinux_2_31_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 Jul 23, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
