From awb
Run Agent Workbench (awb) interactive UI components from Codex or the CLI. Use when the user needs a confirmation, checklist, input, table, code or markdown view, or a visual playground. Always follow interactive runs with awb wait and the returned ID. Use tmux for long-running commands (see awb --help).
npx claudepluginhub joshuarweaver/cascade-ai-ml-agents-misc-1 --plugin lobu-ai-agent-workbenchThis skill uses the workspace's default tool permissions.
1. Ensure the user has the playground open with `awb ui`.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
awb ui.awb run --title "..." <component> [args].awb wait <id> and read the JSON response.Interactive: confirm, checklist, ask
Display: code, table, markdown, plan-viewer, html
--title for every awb run.awb run --help before using a component you are unsure about.awb is not on PATH, ask the user to install or run the local CLI.awb run returns immediately with an ID. Always call awb wait <id> to get the response.
ID=$(awb run --title "Q1" confirm --prompt "Approve?")
awb wait $ID
Fire multiple at once, then wait for each:
ID1=$(awb run --title "Q1" confirm --prompt "Approve?")
ID2=$(awb run --title "Q2" checklist --items "A,B,C")
awb wait $ID1
awb wait $ID2
awb wait <id> returns JSON with the user's response:
{"confirmed": true}
{"items": [{"text":"A","checked":true}]}
{"answers": {"key": "value"}}
confirm
awb run --title "Deploy" confirm --prompt "Deploy to production?"
checklist
awb run --title "Tasks" checklist --items "Build,Test,Deploy"
ask (1-4 questions)
awb run --title "Name" ask --questions '[{"question":"Your name?","header":"name"}]'
awb run --title "Pick" ask --questions '[{"question":"Language?","header":"lang","options":[{"label":"TypeScript"},{"label":"Python"}]}]'
awb run --title "Features" ask --questions '[{"question":"Enable?","header":"feat","multiSelect":true,"options":[{"label":"Auth"},{"label":"API"}]}]'
table
awb run --title "Data" table --data '[{"name":"Alice","age":30},{"name":"Bob","age":25}]'
code (file only)
awb run --title "Source" code --file ./src/index.ts
markdown
awb run --title "Docs" markdown --file ./README.md
awb run --title "Notes" markdown --content "# Hello\n\nWorld"
html
awb run --title "Config" html --content '<html>...</html>'
plan-viewer
awb run --title "Plan" plan-viewer --file ./plan.md
Use tmux for long-running processes. Run awb --help to see your tmux session name.
tmux new-session -A -d -s <session-name>
tmux new-window -t <session-name> -n "dev" "npm run dev"
tmux capture-pane -t <session-name>:dev -p
tmux send-keys -t <session-name>:dev "npm test" Enter
tmux kill-window -t <session-name>:dev