Skip to content

Build a feature with two tools at once

This walkthrough uses a made-up project called example-app. One tool builds an account form while another writes its validation tests.

Open example-app, go to Tasks, and add:

  1. Build the account form
  2. Add account form validation tests

Add details and expected files to each task. If the tests need the form API to settle first, make the test task depend on the form task instead of running them together.

Keep Give each task its own folder on. Keep Finished work needs review on so both results wait for you. Leave automatic next-task selection off for this walkthrough.

You can also keep Let Seggo start tools for me off and copy the prompts yourself.

Open the form task and choose Give to a tool…, then select Codex. Open the test task and give it to Claude Code. Seggo creates a separate task folder and seggo/ branch for each one.

Review the folder and prompt before you open or copy them. Each tool should work only in its returned folder.

Open Working now. You should see both tools and their tasks. If Seggo reports that both tools plan to change the same file, open the warning.

Decide which tool owns that file. Update the task details or pause one task. An overlap warning does not lock the file for you.

Open either task and choose Progress. Checkpoints show completed work, what remains and the next step. If a tool stops, choose Continue in… and hand its task to another tool. The next tool starts from the latest checkpoint in the same task folder.

Finished tasks move to Needs review. Read the summary, changed files and latest checkpoint. Preview the app or run its tests in the task folder.

When the form task looks good, open Ready to merge. Find its row under Ready to merge and choose Merge into main. Then do the same for the tests. If the second branch conflicts with the first, Seggo won’t merge it. Resolve the conflict in that task’s folder, commit, and try again.

Both rows now sit under Already merged. Choose Clean up merged folders…, check the list of folders it will remove and keep, and confirm. Seggo only removes folders whose branch is fully merged and has nothing uncommitted.

Seggo never pushes. When you’re happy with main, push it yourself.