Skip to content

0.7.0 — 2026-11-11

Choose a tag to compare

@github-actions github-actions released this 11 Nov 13:08

Release Notes

The launchpad release. Each repository can now say what you run in it and what
work is waiting, your coding agent can plan across all of them, and cohors
arrives as a Claude Code plugin whose settings decide what Claude may do.
Release builds also carry the browser dashboard inside the binary.

Added

  • The launchpad. cohors now reads what each repository says about itself:
    a committed .cohors/repo.json listing its flows (what to run), the agent
    prompts it ships, and its short-lived tasks. The format is an open
    contract, written down in spec/v1/SPEC.md. Flows are also detected with zero config from
    npm/pnpm/yarn/bun scripts, cargo, uv, Makefile targets, and gradle.
  • cohors launchpad reports the focus board and every open task across the
    fleet (JSON when piped). cohors launchpad validate [PATH] checks one repo's
    contribution, contract prints the rules, and record logs an agent session.
  • Six launchpad MCP tools. launchpad, read_contract, and read_board
    are always on. write_repo_contribution, write_board, and record_activity
    need the new --allow-launchpad flag; each accepts dry_run without it. A
    rejected write lists every problem at once and writes nothing.
  • A Claude Code plugin, installable from this repository as a marketplace:
    the MCP server (found on your machine by a launcher, so the stripped-PATH
    problem goes away), skills for fleet work, setting a repo up, and planning
    focus, and hooks that log each session. The server starts read-only; three
    plugin settings, off by default, let Claude act: Git actions, Run
    commands
    and Launchpad writes (/plugin configure cohors@cohors). A
    refusal from the plugin's server names the setting to turn on.
  • cohors web works wherever cohors is installed. Release builds carry
    the browser dashboard inside the binary (about 2 MB), so it starts at once,
    with no checkout of this repository and no Trunk or Rust toolchain. A build
    from source without the page still builds it with Trunk inside a checkout.
  • One overview, the same everywhere. cohors now works out a single
    briefing for the fleet: what to do next and why (most urgent first, each step
    naming the repos it applies to), six key figures (work not backed up, stashes,
    uncommitted files, stale fetches, open tasks, commits this week), every repo
    with its reasons in plain words, open tasks per repo, and the last seven days
    of commits. The terminal, the browser, the editor extension and the MCP
    server all render that one model, so their numbers cannot disagree.
  • cohors overview prints the briefing at a terminal, with the exact
    command that carries out each step, and the whole model as JSON when piped or
    given --json. An MCP overview tool returns the same thing to an agent.
  • cohors standup prints your commits across every repo for the last seven
    days (or --today) as a paste-ready digest. Standup used to exist only inside
    the dashboard; it is now also an MCP standup tool and a page in the browser
    and the editor extension.
  • cohors agent starts a coding agent on a repo, a task, or the whole
    fleet, with whichever of Claude Code, Codex, Gemini CLI or agy is installed.
    cohors agent run setup-repo asks it to read the current repo and write its
    launchpad file; plan-day plans your focus across every repo; agent runners shows what is installed and why a runner is unavailable. A task
    started this way is linked to its conversation and resumes there next time.
    The five prompts are also served to MCP clients as prompts, and in the
    dashboard a on a repo does the same after asking.
  • A VS Code extension (extension/): the same overview, repositories, tasks and standup in an editor
    tab that follows your theme, reading everything from the cohors binary.
  • The VS Code sidebar is the overview. The cohors container in the activity
    bar holds six panes drawn by the editor itself, so they open, close, reorder
    and hide like Explorer's: Overview (the figures), Do next, Work at risk, Open
    tasks, Commits and Repositories. Each carries its count on its header, the
    activity-bar icon shows how many repositories have work at risk, and a row
    opens the dashboard at that place.
  • The dashboard has the look the terminal has. The mark, large, leads the
    page with the headline and twelve weeks of commits; each section is a card in
    its own colour; a count of zero is a dot. cohors.openOnStartup opens the
    sidebar, the dashboard or both when a window starts.
  • The extension says what it is doing. The Output panel has a "cohors"
    channel with the binary in use and each command it ran, how long it took and
    whether it worked. vscode://rushirb2001.cohors/show opens the dashboard from
    a terminal or a link (it only ever opens the view).
  • A studio for the project's pictures and film. scripts/demo-fleet.sh
    builds a made-up fleet of real repositories in a home folder of its own;
    scripts/studio/build.sh captures cohors on it and renders the README's
    pictures, post images for each place they are shown, and a 37-second film in
    three framings. Nothing in them is mocked up or taken from a real machine.
  • scripts/package-extension.py builds the extension's .vsix with nothing
    but Python, so a release needs no Node tooling.
  • The launchpad contract is in this repository, at spec/v1/SPEC.md, with
    its JSON Schemas.
  • push publishes a branch that was never pushed (git push -u origin HEAD) instead of skipping it. Nothing is forced.
  • ARM Linux release binaries and pip wheels.
  • server.json, the manifest for the official MCP Registry. Each release
    now lists itself there, and uploads its pip wheels, as soon as the release
    build finishes, with no step by hand.
  • Every MCP tool carries annotations: a readable title and whether it only
    reads, may destroy work, is safe to repeat, or reaches the network. Clients
    and MCP directories show these before a call. The server also answers
    resources/list with an empty list instead of an error.

Changed

  • Every surface was rebuilt around what to do next. A quiet neutral
    palette with purple kept for the brand mark and focus. Severity is a block
    with the word in it: a filled RISK (brick red) or WARN (ochre) leads the
    rows of Do next, Work at risk and the repository tables, a quiet outlined
    NOTE or INFO marks the rest, and a clean repo has none. The key figures
    that need attention are filled tiles in the same two colours. Because the
    word carries the meaning, it reads without colour and under NO_COLOR
    (where the block is reverse video).
    • Terminal: the dashboard opens on cards (Do next, Work at risk, Open
      tasks, Commits, Repositories). 1–5 focus a card and each card's border
      lists the keys that act on it. Enter on the repositories card opens a
      detail view: every repo in a two-line list, with state, signals and tasks
      for the one selected. Narrow terminals degrade in a fixed order instead of
      garbling.
    • Browser: a sidebar and one column, with four pages (Overview,
      Repositories, Tasks, Standup), saved views, and a drawer with a repo's full
      detail. Every action previews its targets first. On a read-only server the
      buttons stay and say how to enable them.
  • The browser no longer shows sample data unless asked. A failed load is an
    error with a Retry button, an empty fleet says so, and the demo fleet appears
    only with --demo, labelled as demo data. The guided tour is gone.
  • cohors scan calls its last group "clean" (repos with nothing to report),
    the same definition every other surface uses.
  • The terminal dashboard is made of panels. On a colour terminal every card
    and every overlay is a filled surface instead of a box of lines, with its title
    on a band in its section's colour: purple for Do next, brick for Work at risk,
    sage for Open tasks, slate blue for Commits, teal for Repositories. The focused
    card has the one bright band. Overlays take the colour of the section they
    belong to, and the dashboard behind an open overlay fades, fills included.
    When the terminal is tall enough a blank row separates the header, the figures
    and each band of cards; smaller terminals keep every row for content.
    A panel is a shade off the terminal's real background, so it sits right on any
    colour scheme. cohors asks the terminal for that colour; a terminal that does
    not answer gets line frames in the same section colours instead, because a
    guessed shade is wrong on half of all terminals. The new theme setting
    ("auto", "dark" or "light", also COHORS_THEME) says it outright for a
    terminal that cannot be asked. Without colour (NO_COLOR), or with
    COHORS_CARDS=lines, cards keep their line frames.
  • Quieter rows. A count of zero is a small dot rather than a 0, and a branch
    level with its upstream says nothing rather than level, so the only numbers
    on a row are the ones that mean something. On a wide terminal the repository
    name and branch columns grow to show long names whole.
  • Keys: a letter is one verb on every card. f fetches, p pulls, P
    pushes, c commits and S stashes wherever a repository is under the cursor:
    on Work at risk, in the repository table and in the detail view. On Do next the
    same letters carry out the fetch, pull or push step; a step that only shows you
    repositories (stashes to review, files to commit, a diverged branch) has no
    letter and is opened with Enter, so S and c no longer mean "review" there.
    A repository key pressed on Do next says where it works instead of doing
    nothing. s (standup), t (launchpad), F (fetch everything) and Y (copy
    the standup as markdown, formerly y on the Commits card) work from anywhere.
    A card lists its keys only while it has the focus.
  • Command line. Tab completes commands, sort modes and repository names, and
    cycles through them; Up and Down recall earlier lines; the cursor moves with
    the arrow keys, Home and End, and Ctrl-A, Ctrl-E, Ctrl-U and Ctrl-W work as in
    a shell. A line that is not a command says what was wrong with it
    (commit needs a message: :commit <message>) instead of unknown command, and
    is marked as a failure rather than with a tick.
  • The detail view's list is one line per repository, like the overview's
    table, with the last commit beside it when the terminal is wide enough. The
    path and commit id were repeated under every name; they are in the card about
    the selected repository.

Fixed

  • The browser dashboard listed its roots as full paths; it shows them as
    ~/code, the way the terminal does.
  • With no roots configured, cohors could treat / or the home directory as a
    root when started from there (an editor extension starts it in /), and list
    every tool's checkout on the disk as if it were your work. Neither is ever an
    implied root now, and the VS Code extension runs cohors from the open folder
    (only in a trusted workspace, so opening an untrusted folder never adds it to
    the fleet).
  • The VS Code extension read each Claude Code transcript whole on every change,
    which froze the editor for seconds on a long session. It reads the two ends of
    a large transcript instead.
  • The VS Code extension used the first cohors on the PATH, which on a machine
    with two installs (an older Homebrew or pip one ahead of a newer cargo one,
    both reporting the same version) was the one without cohors overview, so the
    dashboard could not read anything. It now uses the first one that can do the
    job, and when none can, the message names the file that is too old.
  • A terminal that did not say what its background was used to be treated as
    light, which could put light fills on a dark terminal. Not knowing is now its
    own case, and nothing is painted that depends on the answer.
  • On a terminal that did not answer the background question, the first key
    pressed after the dashboard opened was lost. The question is now asked without
    a second reader on the keyboard, and a late answer is still used.
  • The Linux pip wheels were tagged manylinux_2_31 but built against glibc
    2.35. They are now tagged manylinux_2_35, so pip on an older system declines
    the wheel instead of installing a binary that may not start.

Security

  • Text read from a repo's .cohors/ files is labelled as untrusted data to
    the agent, and control characters are stripped before it is printed.
  • Launchpad writes refuse symbolic links at every path they touch.
  • A flow command a repo declares must be one readable line: printable ASCII
    plus letters and digits of left-to-right scripts, at most 400 characters.
    Control characters, invisible characters, line breaks and right-to-left text
    are refused, because they let a command display as one thing and run as
    another. Such a flow is rejected by the validator and never offered.
  • A prompt handed to an agent runner can never be read as a command-line flag,
    and on PowerShell prompt text is never placed on a command line at all.
    Prompt files are private to the user.
  • The editor extension runs nothing a repository supplies (a flow, a declared
    agent, a task) without Workspace Trust and a confirmation that shows exactly
    what will run, resolved first and re-checked just before it starts.
  • Copyable commands in the browser quote repo paths, so a hostile folder name
    cannot inject a command when pasted.

Install cohors-tui 0.7.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/rushirb2001/cohors/releases/download/v0.7.0/cohors-tui-installer.sh | sh

Install prebuilt binaries via Homebrew

brew install rushirb2001/tap/cohors

Download cohors-tui 0.7.0

File Platform Checksum
cohors-tui-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
cohors-tui-x86_64-apple-darwin.tar.xz Intel macOS checksum
cohors-tui-aarch64-unknown-linux-gnu.tar.xz ARM64 Linux checksum
cohors-tui-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum