Step-by-step examples

Follow complete examples that combine projects, remote hosts, review, workbenches, and custom agents.

Work on projects on two remote hosts

Outcome: keep personal and work projects running on their respective machines while using one laptop to direct and review them.

1. Connect Home server and Work server. Configure the desired backends on each.
2. Open your personal website on Home server. On Work server, open the application project and add its API repository as a second root if the task spans both.
3. Start a website agent on Home server and an API investigation agent on Work server. Give each a separate deliverable.
4. Move between the projects and check their conversations. Respond to questions and review completed work.
5. Disconnect the laptop while the remote hosts remain running.
6. Reconnect later and open the original agents. Inspect their results before assigning more work.

What to notice: the laptop is your connection to the work. Project files, backend authentication, and agent execution belong to each host.

Implement with one agent, review with another

Outcome: get an independent reading of a change before accepting it.

1. Create a workbench for the change and launch an implementation agent inside it.
2. Describe the expected behavior and your acceptance criteria. Ask the agent to report when the change is ready for review.
3. Once the files are stable, ask for a Tyde subagent using another available backend to review the implementation without editing.
4. Compare the review findings with the actual diff. Add your own inline comments.
5. Submit the review to the implementation agent, then inspect the revision.
6. Run the project’s required checks, commit, and integrate the finished work.

Review the completed change independently. Focus on empty input, failed requests, and keyboard navigation. Cite concrete locations. Do not edit files or start another implementation.

Create and use a custom reviewer

Outcome: reuse your review standards without retyping them for every conversation.

1. Create a project-review skill on the host.
2. Refresh Skills in settings.
3. Create a custom reviewer definition and assign the skill. Give it a clear output format and appropriate tool access.
4. Launch the reviewer in a project and give it a specific change to inspect.
5. Refine the instructions based on the usefulness of its findings. Use the same definition when launching later reviews on that host.

Use the chapter links in each example for the individual controls and their settings.