claudio-cli-linux-x64 0.1.44 → 0.1.46

package/README.md

@@ -1,5 +1,7 @@
 # claudio-cli
 
+> 🧪 **Open Beta.** Claudio is in active open beta — expect frequent updates, rough edges, and fast iteration on feedback. We're shipping improvements daily.
+
 **You love Claude — so does Claudio.**
 
 Claudio is a plug-and-play AI dev platform that runs on top of your existing [Claude Code](https://www.npmjs.com/package/@anthropic-ai/claude-code) subscription. No Anthropic API key to manage. No per-token API bill eating your budget while agents think. You bring your own Claude Code plan; Claudio wraps it in a terminal experience that orchestrates whole pipelines instead of one-off prompts — for a small flat subscription that costs a fraction of what API-billed dev tools charge for the same work.
@@ -38,9 +40,24 @@ The CLI walks you through `gh` + Claude Code auth on first run. You never paste
 Describe a task. Claudio runs **PM → Designer → Dev → Review → QA → Merge** as a real, observable pipeline against a real GitHub repo. Every stage is a specialized agent; every stage emits structured progress that streams into a live TUI. The output is a merged PR, not a chat transcript.
 
 Two ways to run them:
-- **Work mode** — pick a batch of tasks, Claudio runs them in parallel (1–5 concurrent), re-plans as slots free up.
+- **Work mode** — pick a batch of tasks, Claudio runs them in parallel (1–5 concurrent), re-plans as slots free up, and auto-retries stuck tasks up to 3 times before flagging them for you.
 - **One Shot** — single task, single focused archer firing a constellation of commits. Fastest path from "I want this" to "PR is up."
 
+### Quiet Mode
+Want the agents' horsepower without the GitHub noise? Flip any task to **quiet mode** and Claudio plans, builds, and reviews on a local branch — no issue, no PR, no push. The finished work lands on your **Launch Pad** where you decide whether to open a PR, squash-merge locally, or toss it. Great for spikes, sensitive code, or work you want to eyeball before the rest of the team sees it.
+
+### Launch Pad
+A staging area that collects every piece of in-flight work — quiet-mode branches waiting to ship, PRs with merge conflicts to resolve, reviews ready to submit. Push them out in bulk when you're ready, drop into an interactive conflict resolver, or walk away and come back to them tomorrow. Everything an in-flight claudio session built stays here until you decide its fate.
+
+### Task Manager
+Browse every task you've ever queued — filter by status (new / queued / running / blocked / retry / rejected), create new ones, edit long briefs inline, toggle between ship-a-PR and quiet-local modes, mark tasks as features or bug fixes, and block/unblock them without leaving the terminal. It's also where you recover stuck runs: anything the pipeline left half-claimed gets reconciled back to `new` on entry.
+
+### Doctor
+Your UI feels AI-generated? The Doctor scans your frontend against the industry's sharpest design critique (visual hierarchy, typography, palette intent, layout rhythm, AI-slop anti-patterns), picks a visual direction that fits your project's declared voice, and hands the whole brief to a creative frontend-design agent with authority to rewrite pages, swap the token layer, and create the components a real revamp needs. Not a polish pass — a full aesthetic pivot, shipped as one PR you can revert as a unit.
+
+### Fresh projects
+No repo yet? Claudio can spin one up end-to-end: it asks what you want to build, picks a stack, scaffolds the codebase on your machine, initializes git, creates the GitHub repo, wires in the agent scaffolding (CLAUDE.md, rules/, agent defs), and drops you straight into the pipeline so the first feature can start building while you're still reading the README.
+
 ### Bug Hunt
 Hand Claudio a bug report. It instruments the suspect code, reproduces the scenario, iterates up to 5 times adding more logs each round if the signal isn't enough, pins down the root cause, and lands a fix. Then it **strips all the instrumentation it added** so the PR is just the fix — no debug noise.
 
@@ -60,7 +77,7 @@ Describe a screen, a flow, or a whole section of your product and Claudio produc
 Build a distilled project brief that any future agent can read as context. Captures the design system, the service layout, the code conventions, the "why" behind decisions — in a format the orchestrator injects into later prompts so your agents stop re-discovering the codebase on every run.
 
 ### Imagination
-Compares your product vision (`ROAD.md`) against the reality of your repo and generates net-new tasks that would close the gap. Two modes — "just dream up tasks" or "dream then execute." Great for mornings where you know there's *something* to do but can't name it.
+Compares your product vision (`ROAD.md`) against the reality of your repo and generates net-new tasks that would close the gap. Optionally scope the dream to a specific slice of the codebase (`packages/frontend`, `src/billing`, "my backend only") — Claudio only proposes tasks inside that slice. Two modes — "just dream up tasks" or "dream then execute" — and a choice of horizon (day / week / month). Great for mornings where you know there's *something* to do but can't name it.
 
 ## Why plug-and-play matters
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claudio-cli-linux-x64",
-  "version": "0.1.44",
+  "version": "0.1.46",
   "description": "Bun-compiled claudio-cli binary for linux/x64. Installed automatically by claudio-cli.",
   "license": "MIT",
   "os": ["linux"],