An open source platform to run many agents at a time. Control plane built on CloudFlare, with your agents running on VMs in your cloud provider of choice.
- Tweets56
- Following71
- Followers17
- Likes58
![Screenshot of the SAM (Simple Agent Manager) chat interface. A green system message labeled "[SAM Orchestrator Check-In]" warns that the task appears to have stalled due to several minutes of inactivity. It instructs the agent to send a brief progress update and continue working if unfinished, call complete_task() if finished, or request_human_input() if assistance is needed, warning that otherwise the task will be marked as failed. Below it, the assistant replies: "The work is finished: PR #1436 was pushed, checked, and merged successfully. I'm sending the final SAM task completion signal now so the orchestrator does not mark it stalled." At the bottom is a collapsed tool invocation labeled "Tool: sam-mcp/complete_task" with a green success indicator, showing that the completion signal was sent. The left sidebar displays a list of previous chat sessions.](https://pbs.twimg.com/media/HL9lIUHXwAA2v9B.jpg?name=orig)
ALT Screenshot of the SAM (Simple Agent Manager) chat interface. A green system message labeled "[SAM Orchestrator Check-In]" warns that the task appears to have stalled due to several minutes of inactivity. It instructs the agent to send a brief progress update and continue working if unfinished, call complete_task() if finished, or request_human_input() if assistance is needed, warning that otherwise the task will be marked as failed. Below it, the assistant replies: "The work is finished: PR #1436 was pushed, checked, and merged successfully. I'm sending the final SAM task completion signal now so the orchestrator does not mark it stalled." At the bottom is a collapsed tool invocation labeled "Tool: sam-mcp/complete_task" with a green success indicator, showing that the completion signal was sent. The left sidebar displays a list of previous chat sessions.
ALT Screenshot of the SAM UI on mobile showing a deployment details page for the “staging” environment. The deployment is marked active, with “Release v11” applied and submitted by a user ID. A red “Destroy Env” button appears below the deployment metadata. The Overview tab is selected, showing a status card reading “Unknown — Release v11 applied,” observed Jun 27 08:37 UTC. Below it, summary cards show the node as healthy and routes as published, followed by a public route URL beginning with r1-frontend-3000...apps.simple....
ALT Screenshot of the SAM UI on mobile showing the “staging” deployment details page with “Release v11” applied and the environment marked active. A red “Destroy Env” button appears below the deployment metadata. The “Node & Metrics” tab is selected, showing a deployment node named deploy-01kw07c2 with status badges for Running and Healthy, hosted on hetzner / small / fsn1. Below, a Metrics panel shows CPU at 0.02, memory at 28.6%, and disk at 30.9%. A containers table lists several running containers, including docker-model-runner, with per-container CPU and memory usage. The footer notes node memory usage of 1.1 GiB out of 3.7 GiB.
ALT Screenshot of the SAM UI with the “Deployments” item highlighted in the left sidebar. A large pink arrow points to it, while the main page shows a “Proposed Architecture” document about deployment environment config variables.
ALT Screenshot of SAM showing a staging deployment status summary: commit `0750bcb1` deployed successfully, PR `#1356` is still a draft, Playwright Visual Tests are in progress, and the existing app deployment is still failing because Docker Compose rejects `services.chat.provider`. The public URL still says “SAM deployment node awaiting release.”
