Terminal workflows that
Disclose risk.
Require confirmation.
Define verification.
Include recovery.
Codewright turns terminal work into reviewed procedures for developers and coding agents. You see what changes, how success is proven, and how to recover before you run anything.
- Consequence-aware
Every step exposes impact, risk, and required safeguards.
- Reviewed and reproducible
Structured recipes replace plausible-looking snippets.
- Recovery is part of the plan
Undo and verification are documented before action.
How it works
Know what happens next.
A fuzzy problem becomes a verified fix.
Workflows are more than a searchable list of commands. They run safe diagnostic checks first, branch on real output, and route you to the narrowest applicable recipe.
- 01Problem
A port is already in use
Start with the symptom. Codewright does not pretend the first matching command is automatically the right one.
Intent captured - 02Inspect
Identify the listening process
Run read-only checks first and branch on what the machine actually reports.
Cause isolated - 03Act
Choose the narrowest safe fix
See risk, platform, and confirmation requirements before a state-changing command is rendered.
Action disclosed - 04Verify
Confirm the port is free
The workflow defines its own observable success condition instead of stopping after execution.
Outcome verified
One source / five working surfaces
The safety model travels with the command.
Recipes, workflows, API responses, the CLI, MCP tools, and the agent skill speak the same language for risk, verification, and recovery.
Issue your first work order
Install once. Stop guessing.
Detect your supported agent harness and register Codewright's MCP server and agent skill from one command.
npx @codewright/install