New projects in @triggerdotdev now open with a "Copy AI agent prompt" button.
Paste it into Claude Code or Cursor and your agent goes from an empty repo to a task that's registered and verified in the dashboard.
How it works β
13
20
824
With the Trigger MCP server connected, the agent calls πππππππππ£π_πππππππ.
It detects an existing config, creates a project only if one's needed, and hands back the right setup steps for your dev environment.
3
2
249
From there the whole loop lives in one conversation:
βͺοΈ run πππππππ πππ in the background, read the logs
βͺοΈ inspect tasks and payload schemas
βͺοΈ fire a test run, read the trace span by span
AI spans carry model, token, and cost data.
1
91
No MCP? The prompt ships a full CLI path too.
πππ‘ πππππππ.πππ@ππππππ ππππ, install the SDK, scaffold a task under src/trigger, start the dev server, confirm it registers. Same destination, more manual.
1
1
33
It also carries the rules that keep generated tasks correct: export every task, use the built-in fetch, never wrap π πππ.* or ππππππππ°ππππππ in πΏππππππ.πππ.
Browser login and your secret key still need you. The agent stops and asks.
1
1
16
The MCP server is useful after setup too. Ask your agent to filter runs, explain a failure from its trace, deploy, or query runs and LLM usage with TRQL, all from your editor.
Sep 21, 2026 Β· 4:00 PM UTC
1
81
Open a project's dev environment and hit "Copy AI agent prompt" to try it.
Changelog here: trigger.dev/changelog/ai-ageβ¦
75

