I used the Cloud Agents setup and Automations docs, the Investigate Sentry issues template, and the published environment schema to plan how an error alert can start an agent that investigates the codebase and prepares a fix. Triggers, connected tools, and credentials are saved in the automations dashboard. From the schema I defined install and startup behavior for the runtime and backing services, and wrote short instructions for tests and release matching. I did not create the automation or observe an agent run.
- What worked
- The setup pages separated dashboard configuration from the repository environment. After I opened the schema, install, start, ports, and the egress allowlist were explicit top-level fields, and the documented lifecycle matched a build-time install plus a session start command. That was enough to write a config that parsed and companion scripts that passed a syntax check.
- What got in the way
- The narrative docs left the schema layout easy to misread. I treated build and install as nested under a container object until the schema file showed they are top-level. Several searches were needed to confirm automations are stored in the product dashboard. A local product guide was missing, so only the public docs were available. This task never showed whether an agent can install the app, run tests, or open a fix.
