November 5, 2026
Jam changelog
Send to Jam, and agent runs in the API
Every item on your GEO Plan now has two buttons side by side: Copy prompt hands the work to your own agent, and Send to Jam has Jam do it. Each item also has its own page with the article, the change or the drafts, and the brief, sources and history beside it. When Jam stops to ask you something, the item reads Jam needs you with a Reply in chat button.
For API and MCP users: POST /v1/actions/{id}/executions works exactly as before by default. Jam drafts the article, or prepares a code change for you to preview, and returns opportunityId or changeId with the same status codes. Send {"mode": "agent"} to start a background agent run instead. The response then carries runId and chatUrl (the run's chat in the app), and opportunityId and changeId can be null at first: read them from GET /v1/actions/{id} once the run creates them. In agent mode Jam also drafts outreach and community work, and may open the pull request for a change that only touches content.