Agent mode gives Bright full access: create issues/docs/projects, run sandbox commands, change the workspace, and generate code.

​
Approve the plan as a project

Switch to Agent and send:
Bright creates the project and issues. Open the project link — research from Ask mode usually shows up under Documents.

​
Who does what

Bright will often split ownership:

​
Hand off engineering work

Expand the work section to watch the loop: set a goal → list actions → read/inspect → request repo access if needed → implement → verify.

​
What “done” looks like

Bright connects to GitHub, clones the repo, works on a branch, pushes changes, and opens a pull request. Your job is review → approve → merge. Repo access note during engineering work
If you see a repository access or GitHub 404-style message, connect GitHub (or grant repo access) and retry. Bright can’t implement or push until the repo is reachable.

​
Review the result

The loop ends where it started: with evidence. Open the pull request, read the diff, and check the verification Bright ran. Then trigger one real error and confirm it lands in the Sentry dashboard with a stack trace. If the dashboard is quiet while your API is failing, the wiring isn’t done — send Bright back to the issue with what you saw.

​
Next

Want the same outcome with fewer mode switches? Try the one-shot workflow. Or start fresh with a blank project.