Start agent work from an Orbit record

Give an agent an Orbit module and identify the record you want it to work with.

Before you start

Add the module to the intended project and review its Agent job in Settings. The module’s instructions can ask for code and record updates, so make the current request’s scope explicit.

Select the Orbit module, name the record and section, and state whether the agent may change code or records.

Step by step

1. Open the record and note its exact name, section, and relevant requirements.

2. Open New Agent in the same project. Type a slash and the module name, such as /Analytics, then choose the Orbit entry from the picker.

3. Confirm that the module appears as a chip in the composer. Name the record and section in the request so the agent can find the intended item.

4. Describe the outcome and limits. For a first review, ask for analysis only and explicitly prohibit code or record changes.

5. Check provider, model, access, and project before sending. Read progress and respond to decisions that need your input.

6. Review the result and reopen Orbit to inspect any intended record updates. If implementation was requested, also inspect changed files and test the application behavior.

7. Send a focused follow-up for missing or inaccurate information. A maintained record and a verified implementation are separate outcomes.

What to expect

The agent receives deliberate module context and a clear request about the intended record.

Troubleshooting and useful details

The screenshot shows an unsent Analytics request referencing the proposed project_opened record. Clicking a table row opens its editor; it does not automatically start an agent. Use the module’s slash entry and identify the record in the prompt.