Set up computer permissions from the terminal.
Install BrokenCode Desktop for screen and keyboard control, then run brokencode setup --permissions. macOS presents Accessibility and Screen Recording consent; Windows and Linux use their supported desktop permission flow. A command cannot silently grant these OS permissions. Ordinary terminal coding works immediately without them.
- Routine file, shell, and computer actions run without repeated confirmations.
- Always allow choices are saved for this project across restarts. An explicit deny rule takes precedence.
- Destructive operations, new MCP access, secrets, and repeated failing tool loops can still require attention.
Computer permissions
brokencode setup --permissionsBuilt-in commands keep the session moving.
| Command | Purpose |
|---|---|
| /remote | Open connection controls to connect, reconnect, or pair again |
| /plan <request> | Investigate a change and prepare a plan |
| /goal <objective> | Work toward a persistent session objective |
| /tester [scope] | Test end to end and save reproducible findings, solutions, and review artifacts |
| /developer [scope] | Fix bugs, verify regressions, and prepare a draft PR; inherits Tester’s report in the same session |
| /init | Create or refresh project instructions |
| /undo | Undo the latest reversible change |
| /redo | Restore an undone change |
| /share | Create a shareable session link |
| /help | Open command and keybinding help |
Start an end-to-end testing or repair goal.
Use /tester or /developer with an optional scope. With no scope, Tester examines the current project; Developer uses the preceding Tester objective and saved findings when available. You can hand an unfinished Tester workflow to Developer explicitly. An unrelated unfinished goal must be edited or cleared first.
- Pause, resume, token budgets, and cancellation work as they do for other goals.
- After stopping or restarting, resume explicitly. The role and evidence remain with the session.
- Choose a narrow scope or say local-only when you do not want a draft PR.
- A required environment, credential, or unresolved failure is reported as a blocker rather than a successful completion.
Terminal automation
brokencode run --command tester "Test the login journey and write a report"
brokencode run --continue --command developer "Fix the reported bugs and verify login"Keep an objective across turns.
Start a goal with /goal followed by the result you want. BrokenCode keeps the objective and progress with the session and continues while the goal is active. The desktop goal controls let you pause, resume, edit, or clear it.
- The goal panel shows status and token use.
- Set an optional token budget in the goal editor; work pauses before the next model request when the budget has been reached.
- A budget is a stopping threshold, not an exact cap: the request in progress can exceed it.
- After an interruption or restart, resume the goal explicitly when you are ready.
Start a goal
/goal Implement search, run the relevant checks, and fix any failures.Store the prompt once; call it whenever you need it.
Create Markdown commands under .brokencode/commands for a project or ~/.config/brokencode/commands for every project.
.brokencode/commands/component.md
---
description: Create a typed UI component
agent: build
---
Create a React component named $ARGUMENTS. Match this project's conventions and add focused tests.Commands can accept arguments and current context.
- $ARGUMENTS expands to the full text after the command.
- $1, $2, and later positions select individual arguments.
- Use file references and shell-output blocks when a command needs concrete project evidence.
Run it
/component Button