Code
Code projects
Point WorkPilot at the code you're developing and you can ask for implementations, fixes and investigations with that codebase as the premise. Running the app and executing commands happen in the same window, so the round trip to “does it work?” gets much shorter.
Registering a project
＋New in the sidebar → Code.
Choose the folder — the root of your repository.
The structure is analysed and the file list is read in.
Code is described in the app as reading in a codebase you develop elsewhere, by reference. WorkPilot doesn't duplicate it — it points at the original folder, and it does not move or rename files.
Using it in a thread
Open a thread and equip the project from 📚 Knowledge, roles, connections.
Set the mode to Code.
Say what you want and what the result should be, e.g. “fix the bug in this function”.
For wide-reaching changes, Plan before executing lets you read the intent first. With approval mode on Ask every time, it always pauses before writing (approval mode).
Running it
How the app starts depends on the project.
- If there's a dev server — the start command is detected and run in Terminal. You'll see something like Launched: {command}.
- If it's static HTML — it's served by the built-in server. With several pages, you pick one from a list.
🌐 Open the site in a browser in the thread menu does the same thing.
Running commands
Git operations, builds and tests can be run from the app. Execution happens in Terminal, so your existing environment — SSH keys and all — is used as-is.
Running commands has real consequences. When approval is requested, read the command first. Deletions, force overwrites and pushes to a remote can't be taken back.
Reviewing and reverting changes
For a loaded project you can see the current branch and working state — whether there are uncommitted changes or nothing has moved — so you know what the AI touched before you commit.
If you want the changes gone, reverting returns the files to their state before the work began.
Scanning for secrets
Before code is shared with a team, it's checked for sensitive files. If any are found you'll see a warning like:
⚠️ This code contains {n} sensitive files. Sharing it will sync them to every member's Mac. Do not share production .env files, private keys or .git.
Files placed in a team space are physically synced to members' machines. Hiding them in the UI does not help. If something must not be seen, keep it out of the shared space.
Keeping the list tidy
Code entries can be grouped into folders using the 📁 button on each row — Move to folder, New folder…, Move out of folder. Folders are visual only and don't affect where files actually live.
Where to go next
- Approval mode — deciding how much runs automatically
- Team spaces — working on code together
- Skills — make a development workflow reusable