{"slug": "add-an-app-with-your-coding-agent", "title": "Add an App With Your Coding Agent", "summary": "AppSignal launched Set up with AI, a Labs feature that lets coding agents such as Claude Code, Cursor, and Codex install AppSignal by following Markdown docs and using a short-lived provisioning token that starts with `prov-`. The provisioning URL lets the agent check available resources, create or find an app idempotently, provision a hosted collector, and report setup status, while the page tracks four required steps (app appeared, integration detected, telemetry arriving, requests traced) and two optional logging steps. The token's expiry moves forward one hour per accepted request but is capped at a fixed 24 hours from creation, and users can rotate it or choose Set up by hand instead.", "body_md": "You can now ask your coding agent to set up AppSignal in your application. Give it a prompt, let it follow the installation instructions, and watch a checklist fill in as data starts arriving.\n\nInstalling AppSignal was already straightforward, but it still meant checking your environment, adding the right integration, creating an app, handling credentials, and confirming that telemetry arrived. These are useful checks, but they don't all need your attention. Your agent can work through them while you get on with something else.\n\nWe've been putting the pieces in place to make that possible: installation docs an agent can read, a provisioning API it can use, and a page that shows you how the setup is progressing. It's the first thing you do in AppSignal, and now it's something you can delegate.\n\nSet up with AI was developed in [AppSignal Labs](https://docs.appsignal.com/labs) and is now available to everyone as a Labs feature. It also uses some of the [expert context we released earlier this week](https://blog.appsignal.com/2026/09/21/expert-context-built-with-gorails.html).\n\n## \n\nThe page walks you through three steps:\n\n**Start an agent in your project.** Use any coding agent that can read a URL and edit files, including Claude Code, Cursor, or Codex. The instructions cover Ruby, Elixir, Node.js, Python, PHP, Go, Java, and JavaScript. Your agent follows the instructions for your project.\n\n**Paste the prompt.** The page gives you a short prompt with a copy button. It includes the installation instructions and a provisioning URL for your organization:\n\n**Watch the checklist.** The page checks for progress while your agent works. It tracks four required steps and two optional logging steps:\n\n- An app appeared in AppSignal\n- Integration detected\n- Telemetry arriving\n- Requests traced\n- Log source created *(optional)*\n- Logs flowing *(optional)*\n\nOnce the four required steps are complete, the page takes you to your new app's dashboard.\n\n## \n\nThe prompt can be short because the installation instructions already live in our docs as plain Markdown. The agent starts with [`/agents/new-application.md`](https://docs.appsignal.com/agents/new-application.md), then follows the instructions for your application's language. Those docs have been available for a while, and you can still use them on their own.\n\nThe missing piece was provisioning. An agent could read the instructions, but you still had to create the app, copy a push API key into your project, and check whether data had arrived.\n\nThe provisioning URL connects those steps. It contains a short-lived token that lets the agent use an API to:\n\n- **Check what it can use:** Confirm the token works and see the organization's existing apps, hosted collectors, and endpoints.\n- **Create or find the app:** Resolve it by name and environment and receive its keys. Repeating the same request with the same body returns the same app instead of creating a duplicate.\n- **Provision a hosted collector** if the integration needs one.\n- **Report the result:** Record whether setup succeeded, partially succeeded, or failed, with notes.\n\nYou no longer need to copy keys between windows or create the app separately before configuring it.\n\n## \n\nThe URL contains a credential, so treat it as you would any token you give to a coding agent. Its permissions are limited to provisioning: it can access the information and actions needed for setup, but it can't read telemetry, change your settings, or touch billing.\n\nThe token has two expiry limits. Each accepted request moves its expiry forward by an hour, so an installation that keeps making progress can continue. It also has a fixed 24-hour limit from creation. Rejected requests don't extend either limit.\n\nTokens start with `prov-`, making them recognizable to secret scanners. If you want a new one, select **Rotate this token** on the page. That creates a fresh token and expires the old one.\n\nYou can always choose **Set up by hand** if you don't want to give a credential to an agent.\n\n## \n\nAn agent might take a while or pause to ask you a question. You can leave the page and come back to the checklist to see which steps have completed.\n\nBefore changing your code, the installation instructions run through [five preflight checks](https://docs.appsignal.com/agents/pre-install-checks.md) to confirm the environment is ready. We shaped those instructions with practitioners who deploy Rails applications to production.\n\n## \n\nOnce setup is complete and your application is reporting, your agent can use its signals through AppSignal's context store. Connect it to the [hosted MCP endpoint](https://docs.appsignal.com/mcp-server), which became generally available last week. It now has [additional tools](https://www.appsignal.com/changelog/tools/2026-09-22-mcp-check-ins-search-traces) for check-in monitors, incident search, and deeper traces:\n\nOr give your agent [the CLI](https://docs.appsignal.com/cli) if you want it to work in the same shell as your tests and deploys. [AppSignal for agents](https://docs.appsignal.com/agents) explains when to use each option.\n\nSet up with AI is available through Labs, and we'd like to hear where it gets stuck. Tell the team building it in [our Discord](https://discord.gg/EjF6ykYx63). For step-by-step instructions, see [Add a New Application With AI Agents](https://docs.appsignal.com/guides/install-with-agents).\n\nPublished\n\n## Wondering what you can do next?\n\n## AppSignal monitors your apps\n\nAppSignal provides insights for Ruby, Rails, Elixir, Phoenix, Node.js, Express and many other frameworks and libraries. We are located in beautiful Amsterdam. We love [stroopwafels](https://www.appsignal.com/waffles). If you do too, [let us know](mailto:contact@appsignal.com). We might send you some!\n\n[Discover AppSignal](https://www.appsignal.com)", "url": "https://wpnews.pro/news/add-an-app-with-your-coding-agent", "canonical_source": "https://blog.appsignal.com/2026/09/23/add-an-app-with-your-coding-agent.html", "published_at": "2026-09-23 00:00:00+00:00", "updated_at": "2026-09-23 16:00:30.032100+00:00", "lang": "en", "topics": ["ai-agents", "developer-tools", "ai-tools"], "entities": ["AppSignal", "AppSignal Labs", "Claude Code", "Cursor", "Codex"], "alternates": {"html": "https://wpnews.pro/news/add-an-app-with-your-coding-agent", "markdown": "https://wpnews.pro/news/add-an-app-with-your-coding-agent.md", "text": "https://wpnews.pro/news/add-an-app-with-your-coding-agent.txt", "jsonld": "https://wpnews.pro/news/add-an-app-with-your-coding-agent.jsonld"}}