Cool Workflow

io.github.coo1whitePublished by GitHub account coo1whitev0.1.97Updated Oct 24, 2026

Signed, cited, replayable workflows for Claude, Codex, Gemini, DeepSeek, and other agents.

The publisher's own server: Cool Computers

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local CLI that turns an AI coding agent's answer about a repo into a saved report where every claim cites a real code location.

What you can do
  • Plan a question about a repo or docs folder into small tasks for your own coding agent
  • Produce a report where each claim points to a real code line, blocking results without evidence
  • Verify signed findings offline against a public key and keep tamper-evident ledgers
  • Run commands such as tests and save receipts recording commit, exit code and output digest
  • Resume interrupted runs and reopen saved reports
When to use it
Useful when you want a checkable, replayable record of what an AI coding agent concluded about a codebase, or proof that a test command actually ran, rather than a chat answer that is easy to lose and hard to verify.
Requirements
Runs as a local command-line tool installed from npm (or Homebrew), needing Node.js v22.13 or newer and a terminal; Linux, macOS, or Windows through WSL, with native Windows not yet supported. Real runs need an AI coding agent already installed and logged in on the machine, such as Claude Code or Codex. No API keys are requested.
Before you install
It runs your agent and, with the check command, executes the commands you give it, so only pass commands you intend to run. Reports and run files are written into a .cw folder inside your project. Signature verification only proves signed findings arrived unaltered, not that nothing was added or left out.

Installation

In SourceWeft

  1. Open Cool Workflow in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

What is this?

Cool Workflow (cw) is a small command-line tool that turns your AI coding agent's chat answer — easy to lose, hard to check — into a saved report. Point it at a repo, or any folder of docs, and:

  • It plans the work. Your question becomes a set of small tasks.
  • Your agent does the work. CW never runs a model itself — your own agent reads and thinks.
  • It writes a checked report. Every claim points to a real place in your code, like file.ts:42. A result with no evidence stops instead of passing through.

The model is fuel. CW is the black-box recorder, the dashboard, and the gearbox — never the engine. It never calls a model API, never holds your keys, and never uploads your code.

Before you start

You need two things, and one more for real runs:

  1. A terminal. On macOS: Terminal. On Linux: any. On Windows: install WSL (run wsl --install in PowerShell, then open "Ubuntu" from the Start menu) and type every command below in that Ubuntu window.
  2. Node.js v22.13 or newer. Check with node -v. If it is missing or older, get it from nodejs.org (take the LTS one).
  3. An AI coding agent, for real runs — for one, Claude Code or Codex (see Works with your agent). Not needed for the demo in step 1 of the Quick Start.

Install

bash
npm install -g cool-workflowcw version

cw version prints the version number when the install worked.

Install trouble?
What you seeWhat to do
EACCES: permission deniedDo not use sudo. Put Node in your home folder with nvm, then run the install again.
cw: command not foundClose the terminal and open a new one. If it is still not found, npm prefix -g gives the folder; its bin folder needs to be on your PATH.
Unsupported engine or a Node errorYour Node is older than v22.13: update it (node -v to check).
Or install with Homebrew
bash
brew tap coo1white/cool-workflow https://github.com/coo1white/cool-workflowbrew install coo1white/cool-workflow/cool-workflowcw version

Upgrade later with brew update && brew upgrade cool-workflow.

You need: Node.js v22.13 or newer. No agent yet? Step 1 below still works — CW never runs a model itself.

Runs on: Linux, macOS and Windows through WSL. Native Windows is not yet supported: CI runs it to measure what still fails, and that work is going on.

Works with your agent

AgentFlagStatusGet it
Claude Code-claude✅ worksinstall
Codex CLI-codex✅ worksinstall
Muse Code-muse✅ works—
OpenCode-opencode✅ worksinstall
Gemini-gemini✅ through opencodeinstall OpenCode
DeepSeek-deepseek✅ through opencode or an HTTP endpointinstall OpenCode
GitHub Copilot CLI-copilot🧪 betainstall
Antigravity-antigravity🧪 betainstall
Grok-grok✅ works (add -grok)install
Cursor—⬜ not yet
Aider—⬜ not yet
Qwen Code—⬜ not yet
Kimi—⬜ not yet

🧪 beta: CW has a wrapper and an offline test for it, but no real login has passed cw doctor --conformance yet, and cw never picks it by itself: add its flag.

Log in to your agent once on its own (run it, for one claude, and follow its steps) before you use it with CW: CW uses your agent as it is set up, and never asks for your keys.

Not sure what you have? cw doctor checks your setup and cw fix prints the commands that put it right.

Quick Start

1 · See it work — 30 seconds, no agent needed

bash
cw demo tamper# → builds a real signed ledger, forges it three ways, catches all three offline# → VERDICT: tamper-evidence holds ✓

2 · Ask a question about your code — one command

bash
cw -q "How does auth work end-to-end here?"

CW uses the current repo and the first agent it finds on your PATH. Want a specific agent? Add a flag from the table above, such as -claude.

A full review takes about 4 minutes on a real repo (14 workers; the Map and Assess stages run at the same time). One focused question? Add --fast: 6 workers in place of 14, the same cited answer for fewer agent calls.

3 · Open the report

The report opens in your browser by itself when the run ends. It starts with the answer, then the evidence behind it. Later, open it again with:

bash
cw report --open

Want to see one first? A real run's Workbench and report, rebuilt on every push: coo1white.github.io/cool-workflow (the report is at /report.html).

4 · Keep proof that your tests passed

An agent that says "all tests pass" has only said it. Run the tests through CW and keep a receipt:

bash
cw check -- npm test# → ✓ passed: npm test (exit 0 at 1a2b3c4) — receipt rc-…. Cite it as receipt:rc-…

CW runs your command (never a model) and saves what happened: the commit, the exit code, a digest of the output. A result that cites receipt:rc-… is checked again before it counts: a failed run, a missing receipt, or code that changed since the run is turned down, with the one command to fix it. cw check list shows your receipts.

These steps are the core path. Everything else is kept working, not grown.

Words you will see

WordWhat it means
agentThe AI coding tool on your machine (Claude Code, Codex, …) that does the reading and thinking. CW gives it small tasks.
runOne question, from start to report. Each run has an id, and its files are kept in .cw/runs/<id>/ in your project.
reportThe answer, with the evidence for each claim (file.ts:42). Kept as report.md, and opened in your browser.
evidenceA pointer to a real line of code. A claim without it is not let through.
receiptA record, from cw check, that a command (for one, your tests) truly ran and how it ended.
resumeGoing on with a run that stopped: cw --resume --run <id>.

Can You Trust the Report?

CW does not run the model — it keeps the books. Your agent signs its findings (ed25519), and cw report verify-bundle checks — offline, with only the public key — that every signed finding is in the report unaltered. CW holds no private key: the agent signs, CW only verifies. This proves the signed findings reached you unaltered — not that nothing else was added, and not that none were left out. See the Trust Model.

Troubleshooting

ProblemFix
No agent foundcw doctor — shows which agents are on your machine
status: blockedSet CW_AGENT_COMMAND=builtin:claude or pass -claude
claude: command not foundInstall Claude Code and run again
Where is my report?<repo>/.cw/runs/<id>/report.md, or run cw report --open
Missing required input: questionAdd -q "<question>"
Run stopped before the endFix the cause, then cw --resume --run <id> takes it to the end; a worker that stopped gets fresh tries (inside the project, or add --repo <path>)
... is not a git projectRun it inside the project, or pass --repo
Run <id> was made for <folder>The run belongs to another folder (a copied or moved repo): pass --repo <that folder>, or move it with cw run export and cw run import

Learn more

CW dogfoods its own release: every cut runs release-cut against this repo.

License

BSD-2-Clause. Built by COOLWHITE LLC.

Source: README.md at commit 48e12f2

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.97LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Cool integrations