Foreman kit · component 4 of 8
ToolBelt
src/components/kit/ToolBelt.astro: the pegboard, the agent's belt, the kraft tags and the example run. Every instance emits fm:kit events and listens for fm:kit:cmd.
Defaults, on cream
Workshop · repo atlas
Load the belt
Tap a tool to hang it on the agent's belt. Tap it again to put it back on the board.
- GitHub
- Linear
- Slack
- Langfuse
- MCP
- Sandboxes
- GitLab
Connections belong to the repository, so every new workspace in atlas starts with this belt.
7 of 7 tools on the belt
The tags on the belt
Each tool's tag says what the agent can do with it and what stays held for you. Change a setting and the run below changes too.
Still on the board
Example run: ENG-123, start to finish
8 of 8 steps work with this belt. Missing tools grey out their steps.
Linear
Starts from ENG-123, “Login loops after sign-in”. The agent reads the issue and its comments.Starts from ENG-123. Foreman reads the issue in; the agent gets no Linear tools.Starts from ENG-123. The agent reads it and comments its plan on the issue.
foreman run issue ENG-123Hang Linear on the belt to start from an issue. Without it, you type the task.
Workspace
Workspace osaka: its own git worktree on
eng-123-login-loop.Workspace osaka runs in a E2B sandbox, oneng-123-login-loop. Provider keys stay on your computer.Workspace osaka runs in a Daytona sandbox, oneng-123-login-loop. Provider keys stay on your computer.Workspace osaka runs in a Vercel Sandbox sandbox, oneng-123-login-loop. Provider keys stay on your computer.Workspace osaka runs in a Docker sandbox, oneng-123-login-loop. Provider keys stay on your computer.Langfuse
Reads the trace of the failing
POST /login: the redirect fires before the session is saved.Hang Langfuse to let the agent read your app's traces.Langfuse access is Nothing, so no traces for this agent.
MCP
Checks itself with
foreman-app. Delegation is off, so it writes the regression test too.Hands “add a regression test” to lisbon withstart_task, then reads the reply.Hang MCP to see what an agent can do with Foreman's own tools.
Pull request
Pushes the branch and opens draft PR #42 on GitHub.Pushes the branch and opens draft MR !42 on your GitLab.
foreman pr create atlas --draftHang GitHub or GitLab to push and open the pull request.
CI
CI fails: Tests, 1 failing. Foreman saw it, so you don't have to refresh.The pipeline fails, and Foreman tells you.
Hang a code host to watch CI.
Back to green
Auto-fix is off: Home shows CI failed and you press Fix CI in…. Checks pass.Auto-fix sends the failing log to the tab: fix 1 of 2 for this commit. Checks pass.
Hang GitHub to watch CI and fix it.This demo draws the CI loop on GitHub. Hang the wrench to see it.
Slack
Drafts “PR #42 is ready for review” to @maya, the reviewer. It waits for your Send.Sends “PR #42 is ready for review” to @maya. The rule has your consent.The agent also posts the fix to #launches.
Hang Slack to tell the reviewer.Slack rules fire on pull request events. Hang a code host first.
Merging stays with you: press Merge, or foreman pr merge atlas --auto to merge when the checks pass. Linear’s own GitHub integration moves ENG-123 along. Illustrative run; the names are made up.
Dark night theme, a second instance
Night shift · repo atlas
Pack the night shift's belt
Tap a tool to hang it on the agent's belt. Tap it again to put it back on the board.
- GitHub
- Linear
- Slack
- Langfuse
- MCP
- Sandboxes
- GitLab
Connections belong to the repository, so every new workspace in atlas starts with this belt.
7 of 7 tools on the belt
The tags on the belt
Each tool's tag says what the agent can do with it and what stays held for you. Change a setting and the run below changes too.
Still on the board
Example run: ENG-123, start to finish
8 of 8 steps work with this belt. Missing tools grey out their steps.
Linear
Starts from ENG-123, “Login loops after sign-in”. The agent reads the issue and its comments.Starts from ENG-123. Foreman reads the issue in; the agent gets no Linear tools.Starts from ENG-123. The agent reads it and comments its plan on the issue.
foreman run issue ENG-123Hang Linear on the belt to start from an issue. Without it, you type the task.
Workspace
Workspace osaka: its own git worktree on
eng-123-login-loop.Workspace osaka runs in a E2B sandbox, oneng-123-login-loop. Provider keys stay on your computer.Workspace osaka runs in a Daytona sandbox, oneng-123-login-loop. Provider keys stay on your computer.Workspace osaka runs in a Vercel Sandbox sandbox, oneng-123-login-loop. Provider keys stay on your computer.Workspace osaka runs in a Docker sandbox, oneng-123-login-loop. Provider keys stay on your computer.Langfuse
Reads the trace of the failing
POST /login: the redirect fires before the session is saved.Hang Langfuse to let the agent read your app's traces.Langfuse access is Nothing, so no traces for this agent.
MCP
Checks itself with
foreman-app. Delegation is off, so it writes the regression test too.Hands “add a regression test” to lisbon withstart_task, then reads the reply.Hang MCP to see what an agent can do with Foreman's own tools.
Pull request
Pushes the branch and opens draft PR #42 on GitHub.Pushes the branch and opens draft MR !42 on your GitLab.
foreman pr create atlas --draftHang GitHub or GitLab to push and open the pull request.
CI
CI fails: Tests, 1 failing. Foreman saw it, so you don't have to refresh.The pipeline fails, and Foreman tells you.
Hang a code host to watch CI.
Back to green
Auto-fix is off: Home shows CI failed and you press Fix CI in…. Checks pass.Auto-fix sends the failing log to the tab: fix 1 of 2 for this commit. Checks pass.
Hang GitHub to watch CI and fix it.This demo draws the CI loop on GitHub. Hang the wrench to see it.
Slack
Drafts “PR #42 is ready for review” to @maya, the reviewer. It waits for your Send.Sends “PR #42 is ready for review” to @maya. The rule has your consent.The agent also posts the fix to #launches.
Hang Slack to tell the reviewer.Slack rules fire on pull request events. Hang a code host first.
Merging stays with you: press Merge, or foreman pr merge atlas --auto to merge when the checks pass. Linear’s own GitHub integration moves ENG-123 along. Illustrative run; the names are made up.
Compact, four tools, no teaser
Workshop · repo atlas
Load the belt
Tap a tool to hang it on the agent's belt. Tap it again to put it back on the board.
- GitHub
- Linear
- Slack
- MCP
Connections belong to the repository, so every new workspace in atlas starts with this belt.
4 of 4 tools on the belt
The tags on the belt
Each tool's tag says what the agent can do with it and what stays held for you. Change a setting and the run below changes too.
Still on the board
Example run: ENG-123, start to finish
7 of 7 steps work with this belt. Missing tools grey out their steps.
Linear
Starts from ENG-123, “Login loops after sign-in”. The agent reads the issue and its comments.Starts from ENG-123. Foreman reads the issue in; the agent gets no Linear tools.Starts from ENG-123. The agent reads it and comments its plan on the issue.
foreman run issue ENG-123Hang Linear on the belt to start from an issue. Without it, you type the task.
Workspace
Workspace osaka: its own git worktree on
eng-123-login-loop.Workspace osaka runs in a E2B sandbox, oneng-123-login-loop. Provider keys stay on your computer.Workspace osaka runs in a Daytona sandbox, oneng-123-login-loop. Provider keys stay on your computer.Workspace osaka runs in a Vercel Sandbox sandbox, oneng-123-login-loop. Provider keys stay on your computer.Workspace osaka runs in a Docker sandbox, oneng-123-login-loop. Provider keys stay on your computer.MCP
Checks itself with
foreman-app. Delegation is off, so it writes the regression test too.Hands “add a regression test” to lisbon withstart_task, then reads the reply.Hang MCP to see what an agent can do with Foreman's own tools.
Pull request
Pushes the branch and opens draft PR #42 on GitHub.Pushes the branch and opens draft MR !42 on your GitLab.
foreman pr create atlas --draftHang GitHub to push and open the pull request.
CI
CI fails: Tests, 1 failing. Foreman saw it, so you don't have to refresh.The pipeline fails, and Foreman tells you.
Hang a code host to watch CI.
Back to green
Auto-fix is off: Home shows CI failed and you press Fix CI in…. Checks pass.Auto-fix sends the failing log to the tab: fix 1 of 2 for this commit. Checks pass.
Hang GitHub to watch CI and fix it.This demo draws the CI loop on GitHub. Hang the wrench to see it.
Slack
Drafts “PR #42 is ready for review” to @maya, the reviewer. It waits for your Send.Sends “PR #42 is ready for review” to @maya. The rule has your consent.The agent also posts the fix to #launches.
Hang Slack to tell the reviewer.Slack rules fire on pull request events. Hang a code host first.
Merging stays with you: press Merge, or foreman pr merge atlas --auto to merge when the checks pass. Linear’s own GitHub integration moves ENG-123 along. Illustrative run; the names are made up.
No header, no run strip, in a 420px column
- GitHub
- Linear
- Slack
- Langfuse
- MCP
- Sandboxes
- GitLab
Connections belong to the repository, so every new workspace in atlas starts with this belt.
7 of 7 tools on the belt
Commands and events
Events appear here.