Code Development

Before you begin

• A clean branch or a recorded set of existing local changes
• A narrow scope, forbidden directories, and acceptance commands
• The required runtime, package manager, and credentials

1. Reference the relevant files and ask the agent to summarize current behavior.
2. Give the target behavior, edge cases, and test commands; request a plan first.
3. Keep Manual approve and review every write and shell command.
4. Run focused tests, then project checks.
5. Review the diff for secrets, generated files, and unrelated refactors.

›_Copyable prompt

Inspect @apps/desktop/src/renderer/features/thread/. Explain the current message-list positioning behavior and propose the smallest fix. Change only relevant source and tests, run the focused tests, and report failures. Do not reset git, delete files, or access paths outside the workspace.

◇

Approval checkpointConfirm the working directory, command arguments, and side effects before allowing shell operations.

✓

Expected resultA reviewable diff with a plan, changed-file list, test output, and remaining risks.

The edit is shown as an expandable diff while command states and workspace files remain in the same task surface.

What is different in Wordless

The value is not merely writing code: each command, permission, diff, and test result stays aligned to one task. @ references narrow the context, approval cards show the real command, and the original failure log remains available for a targeted continuation.

Scenario	Key capability	Verification
Diagnose a regression	Narrow @ scope, search, original logs	Cause first, then the smallest diff
Implement a feature	Plan, edit, test, review	Focused and project checks remain visible
Controlled commands	Default Access, approval, one-time elevation	Working directory and arguments are explicit