Skip to main content

Harness

Coding

Open the project folder. If you have not set another mode, the session is coder.

The plan​

The first reply is a short plan. It names the files, the commands, and the risks. Nothing is written until you approve.

Allow on the plan starts the work. You can turn on auto-approve for this session only. It ends when the session ends. The next session asks again.

Refuse, and the folder stays as it was. You can ask for a different plan.

What it does after you allow​

It edits, then reads the file back. When it can find the project’s test or lint command, it runs that command. If the command fails, it tries a fix once or twice. Then it stops and says what changed.

Stop and undo​

Stop interrupts the work in progress.

Undo restores the last change this session made. It is not a git reset. Commits you made yourself, and files this session did not touch, stay where they are.

Git in the window​

The window shows git status and the diff.

Commit asks first. It does not push. It only includes files this session touched. Other changes in the working tree are left unstaged.

If you want a remote update, you do that yourself, outside this step.