Build, plan & review

Written By Stanislas

Last updated 7 days ago

Overview

How Swiftask Code works on your project: choosing a mode, planning bigger work, controlling approvals, and reviewing changes.

Prerequisites

  • Swiftask Code installed and signed in
  • A basic understanding of the chat panel (see Chat & context)

Step-by-step guide

1. Choose the right mode

Your goalMode
Fix a bug, add a feature, run testsBuild
Learn the codebase, ask questions, code review (no edits)Ask
Scope a large change before touching codePlan

Pick a mode in the chat input based on what you want to happen.

Build, Ask, and Plan modes

2. Understand the three modes

Build (default) β€” for implementing features, fixing bugs, refactoring, running tests. Swiftask Code can search your project, edit files, and run commands.

Ask β€” for learning the codebase, architecture questions, review without edits. Swiftask Code reads and searches only.

Plan β€” for larger work where you want a written plan before any code changes. Swiftask Code researches your project and writes a structured plan. It won't edit source files until you choose Build.

BuildAskPlan
Answer questionsYesYesYes
Change source filesYesNoNo
Run commandsYesNoNo
Create a written planNoNoYes

3. Plan before you build (for non-trivial work)

  1. Switch to Plan mode
  2. Describe what you want β€” scope, constraints, anything important
  3. Swiftask Code produces a plan you can read in chat
  4. Open it from the Plans library (checklist icon) to read or edit
  5. When you're satisfied, click Build to start implementation in Build mode

You can stay in Plan mode and ask for updates to the same plan before building.

Plan generated in chat
Plans library
Build button on a saved plan

4. Control what runs automatically

In Swiftask Settings β†’ Permissions, choose how much Swiftask Code can do without asking:

SettingExperience
Run everythingSwiftask Code proceeds on file edits and commands without stopping you (except when it needs a clarifying answer)
Ask before sensitive actionsYou confirm before file changes; commands only run automatically if they match your trusted commands list

Trusted commands are shell commands you're comfortable auto-approving β€” for example yarn test, npm run typecheck, or git status. Edit the list in Settings.

File edits always ask for confirmation in Ask before sensitive actions mode.

Permissions settings

5. Review file changes

In Build mode, when Swiftask Code changes files, you review before moving on.

In the chat β€” a Files changed section lists what was modified. You can:

  • Keep all β€” accept every change
  • Undo all β€” revert everything from that turn
  • Open a diff per file
  • Keep or undo one file at a time
Files changed in chat
File diff viewer

In the editor β€” on a changed file, the title bar may show Keep agent edits and Undo agent edits.

6. Track progress on multi-step tasks

On multi-step tasks, Swiftask Code may show a checklist in the chat so you can see what's done and what's left β€” especially useful during Plan β†’ Build work.

Progress checklist

Practical use cases

Copy and adapt these prompts β€” pick the mode first, then paste into chat.

Build mode:

TaskSample prompt
Fix a bugWhen I run the tests I get this error: [paste error]. Find the cause and fix it. β€” @-mention the test file or terminal output
Small featureAdd [feature]. Match the existing UI style and run the type checker when you're done.
Run testsRun the project test suite and fix any failures. β€” add the command to trusted commands if you use ask-first mode
Focused refactorExtract [logic] from this file into a shared helper and update callers. Don't change behavior.

Review Files changed before Keep all.

Plan mode:

TaskSample prompt
Large featurePlan how to add [feature]: scope, UI, risks, and open questions. Don't write code yet.
Wide refactorPlan a rename of [old] to [new] across the codebase, including tests and docs.

Read the plan in the Plans library, adjust if needed, then click Build.

More read-only examples (explore codebase, code review) are in Chat & context.

Tips & best practices

Tip: Describe the outcome ("add session collections with list UI") not every file to touch β€” Swiftask Code will discover those during planning.

Ask first if unsure: List the main places that depend on [module]. β€” then switch to Plan or Build.

Auto-format: optional β€” Settings β†’ Permissions β†’ Auto-format on finish runs your formatter on edited files after each turn.

Approval examples:

SituationWhat you seeAction
File edit (ask-first mode)Permission card with file pathAllow or Deny
Shell command not in trusted listCommand previewAllow once or add to trusted
Ambiguous requestMultiple-choice clarify promptPick the option that matches your intent

Additional resources

  • Chat & context β€” sessions, @-mentions, Ask mode examples
  • Customize β€” rules and permission defaults
  • Help & FAQ β€” tips, approvals, and edit issues