Coding agent

What it does#

Technical SEO fixes and review-ready code changes. It works from the active website’s company source and the specific brief you provide. Use it for a bounded channel task, then inspect the output before using it.

Before you run it#

Reviewed company and strategy documents; page evidence and the intended GitHub repository connection for connected code work.

Read the current readiness panel in Agent Operations or Setup & Fixes. Missing strategy documents can block even a draft; provider configuration may separately block connected execution.

Run and inspect#

1. Open the Coding agent for the intended website and review its supported settings.
2. Choose a specific objective and provide approved source material.
3. Start one run and inspect its status before repeating it.
4. Review the output: Technical recommendations or bounded review-ready changes where repository access is available.
5. Request changes or approve the exact version. Use a separate supported delivery action when appropriate.

Review checklist#

Inspect the diff, tests and deployment impact. A proposed patch or pull request is not a merged and deployed fix.

Verify sources and remove unsupported claims. Keep sensitive provider actions under the normal approval workflow; agent configuration does not override it.

Example brief#

Example request

Propose a minimal fix for this verified canonical issue. Explain the tests and rollback considerations, and do not merge or deploy.

If it is blocked#

Read the named requirement and resolve that stage. A provider-unavailable state may require Obelo’s team, while missing company information can be addressed in the workspace. Do not invent a result or substitute an unrelated connection.