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

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

Total release size: 20.2 MB

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

Download URL cohors-0.7.4-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
5b2e660d3b5a5ccc05d262c2c9ef65ec24726123e978ff2f6c272f6729405139
BLAKE2b-256 checksum
How to use checksums
2e976b72baf9b5e3cb29393b7823823c53e0605a10420e1dd054d95b848be2fb
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.4-py3-none-manylinux_2_35_aarch64.whl

Download URL cohors-0.7.4-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
597d61c7ba2e6c38ea9ec2ebe5a949a867576b5fe01f67fe0e28c45eb96d914b
BLAKE2b-256 checksum
How to use checksums
65f3ac457142681ecee0751dc648dd114e2377840a4d87a752c320d5d357c324
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.4-py3-none-macosx_11_0_arm64.whl

Download URL cohors-0.7.4-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
58df0861056219aee390468c70964cce15c8f305626571696e9831fd441918cf
BLAKE2b-256 checksum
How to use checksums
11f975d0c67a40cfea15bf48e2681e0dcf99e8a7d6636ef1c6dfa881de2d0129
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.4-py3-none-macosx_10_12_x86_64.whl

Download URL cohors-0.7.4-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
2cf00983dcbb6c8c85c72d2982bccf5bc2e15d8db250a7d147d688c768d7f4a3
BLAKE2b-256 checksum
How to use checksums
e394fa62842ffa306a149613a3b97fd89dbd3290af43be31378f3c5b53c99317
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.4

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