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 --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 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.2

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.2
File Actions
cohors-0.7.2-py3-none-manylinux_2_35_x86_64.whl Python 3 none Linux glibc 2.35+ x86-64 Details for cohors-0.7.2-py3-none-manylinux_2_35_x86_64.whl
cohors-0.7.2-py3-none-manylinux_2_35_aarch64.whl Python 3 none Linux glibc 2.35+ ARM64 Details for cohors-0.7.2-py3-none-manylinux_2_35_aarch64.whl
cohors-0.7.2-py3-none-macosx_11_0_arm64.whl Python 3 none macOS 11.0+ ARM64 Details for cohors-0.7.2-py3-none-macosx_11_0_arm64.whl
cohors-0.7.2-py3-none-macosx_10_12_x86_64.whl Python 3 none macOS 10.12+ x86-64 Details for cohors-0.7.2-py3-none-macosx_10_12_x86_64.whl

Total release size: 20.2 MB

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

Download URL cohors-0.7.2-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
6a33233c2e6457dcd883d495f248d2272601264e8842640347583fe42ec003c3
BLAKE2b-256 checksum
How to use checksums
eaa8da7415b69ee7d387d0cf1170ac0990033ce9d60a7da4f6e891c4087a653d
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.2-py3-none-manylinux_2_35_aarch64.whl

Download URL cohors-0.7.2-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
f118b2d1d60a6e3b7d93ef29437028438fc31a64272abe6f04530977bc8f7dc5
BLAKE2b-256 checksum
How to use checksums
e26b692adeb193964f670ce4c6b1474f28492ac72acacc747681c30617974ff7
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.2-py3-none-macosx_11_0_arm64.whl

Download URL cohors-0.7.2-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
5480da57abc2f19e775327b6f1f2084a0be7a529567a0549624eb8053f8ec595
BLAKE2b-256 checksum
How to use checksums
332031da28e6c50c46f7600f323957feeb30afbf7bed65985ecb82cf70a2db20
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.2-py3-none-macosx_10_12_x86_64.whl

Download URL cohors-0.7.2-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
f757b54f76bc84affc4eca854eeb6172af0272ddb1ad38a098d542afc74e87e1
BLAKE2b-256 checksum
How to use checksums
7fef82520544da98c8d0ed07117a6575c026fb57e9a5279633f7fcd1aabc494e
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.2

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.2-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