Skip to content

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.

  1. GitHub
  2. Linear
  3. Slack
  4. Langfuse
  5. MCP
  6. Sandboxes
  7. 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.

  • Wrench · gh or a token

    GitHub
    Auto-fix CI

    Commit, push and open draft PRs. Merge, or auto-merge when checks pass. Watch CI and reviews. Start from an issue or PR link. Open PRs in GitHub or Graphite.

    A failing CI run waits on Home with Fix CI in… for you to press.

    Auto-fix sends the failing log to the tab you picked: 2 fixes a commit, 5 a PR. Never for review comments.

    Agents in repositories that use it get GH_TOKEN. Turn approvals on to see each push first.

  • Level · an API key

    Linear
    What agents may do

    Agents get no Linear tools. Foreman still reads issues for New workspace.

    Agents can search and read issues, projects and comments.

    Agents can also create and update issues and comment.

    Nothing goes to Linear from an agent.

    They can't create, edit or comment.

    Issue text is written by others, so treat this like any tool that changes things.

    Foreman doesn't change issue status itself.

  • Megaphone · a bot token

    Slack
    What agents may do
    Rule: PR ready → message the reviewer

    Foreman sends your notification rules. Agents can't post.

    Agents may also post to #launches, the channel you allowed.

    Messages to anyone but you wait for your Send.

    This rule has your consent; change any part of it and it asks again.

    Outbound only. Never pings @here or @channel.

  • Magnifier · a key pair

    Langfuse
    What agents may do

    Agents get no Langfuse tools.

    Agents get search_observations, get_trace and get_observation.

    They can't change anything in Langfuse.

    Langfuse Cloud EU, US or HIPAA, or your own host over HTTPS.

  • Power strip · built in

    MCP
    Let agents start workspaces

    Every workspace agent gets foreman-app: its status, its checks, a preview, its own chat history.

    No agent can start a workspace or queue a message.

    Agents can hand tasks to other workspaces in atlas and read the replies. Other repositories are refused.

    MCP servers a repository proposes start only after you approve them.

  • Toolbox · experimental

    Sandboxes
    Where the workspace runs

    E2B · Hosted · 1-hour sessions on Hobby · 2, 4 or 8 vCPUs.

    Daytona · Hosted · 24-hour sessions · 1, 2 or 4 vCPUs.

    Vercel Sandbox · Hosted · 45-minute sessions on Hobby · 2, 4 or 8 vCPUs.

    Docker · This computer, or another over SSH · No session limit · 1 to 8 vCPUs.

    Off by default. Provider keys never enter the sandbox. Needs a GitHub remote. Claude Code, Codex and OpenCode, not Cursor.

    Turns keep going after you quit, up to the provider's session limit.

  • Pliers · an access token

    GitLab

    gitlab.com or self-managed

    Merge requests and issue links work like GitHub's, on your own GitLab host.

    Fewer events: employee triggers don't see failed pipelines, approvals or requested changes.

    foreman gitlab add https://gitlab.example.com

Example run: ENG-123, start to finish

8 of 8 steps work with this belt. Missing tools grey out their steps.

  1. Linear

    Starts from ENG-123, “Login loops after sign-in”. The agent reads the issue and its comments.foreman run issue ENG-123

  2. Workspace

    Workspace osaka runs in a E2B sandbox, on eng-123-login-loop. Provider keys stay on your computer.

  3. Langfuse

    Reads the trace of the failing POST /login: the redirect fires before the session is saved.

  4. MCP

    Checks itself with foreman-app. Delegation is off, so it writes the regression test too.

  5. Pull request

    Pushes the branch and opens draft PR #42 on GitHub.foreman pr create atlas --draft

  6. CI

    CI fails: Tests, 1 failing. Foreman saw it, so you don't have to refresh.

  7. Back to green

    Auto-fix is off: Home shows CI failed and you press Fix CI in…. Checks pass.

  8. Slack

    Drafts “PR #42 is ready for review” to @maya, the reviewer. It waits for your Send.

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.

  1. GitHub
  2. Linear
  3. Slack
  4. Langfuse
  5. MCP
  6. Sandboxes
  7. 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.

  • Wrench · gh or a token

    GitHub
    Auto-fix CI

    Commit, push and open draft PRs. Merge, or auto-merge when checks pass. Watch CI and reviews. Start from an issue or PR link. Open PRs in GitHub or Graphite.

    A failing CI run waits on Home with Fix CI in… for you to press.

    Auto-fix sends the failing log to the tab you picked: 2 fixes a commit, 5 a PR. Never for review comments.

    Agents in repositories that use it get GH_TOKEN. Turn approvals on to see each push first.

  • Level · an API key

    Linear
    What agents may do

    Agents get no Linear tools. Foreman still reads issues for New workspace.

    Agents can search and read issues, projects and comments.

    Agents can also create and update issues and comment.

    Nothing goes to Linear from an agent.

    They can't create, edit or comment.

    Issue text is written by others, so treat this like any tool that changes things.

    Foreman doesn't change issue status itself.

  • Megaphone · a bot token

    Slack
    What agents may do
    Rule: PR ready → message the reviewer

    Foreman sends your notification rules. Agents can't post.

    Agents may also post to #launches, the channel you allowed.

    Messages to anyone but you wait for your Send.

    This rule has your consent; change any part of it and it asks again.

    Outbound only. Never pings @here or @channel.

  • Magnifier · a key pair

    Langfuse
    What agents may do

    Agents get no Langfuse tools.

    Agents get search_observations, get_trace and get_observation.

    They can't change anything in Langfuse.

    Langfuse Cloud EU, US or HIPAA, or your own host over HTTPS.

  • Power strip · built in

    MCP
    Let agents start workspaces

    Every workspace agent gets foreman-app: its status, its checks, a preview, its own chat history.

    No agent can start a workspace or queue a message.

    Agents can hand tasks to other workspaces in atlas and read the replies. Other repositories are refused.

    MCP servers a repository proposes start only after you approve them.

  • Toolbox · experimental

    Sandboxes
    Where the workspace runs

    E2B · Hosted · 1-hour sessions on Hobby · 2, 4 or 8 vCPUs.

    Daytona · Hosted · 24-hour sessions · 1, 2 or 4 vCPUs.

    Vercel Sandbox · Hosted · 45-minute sessions on Hobby · 2, 4 or 8 vCPUs.

    Docker · This computer, or another over SSH · No session limit · 1 to 8 vCPUs.

    Off by default. Provider keys never enter the sandbox. Needs a GitHub remote. Claude Code, Codex and OpenCode, not Cursor.

    Turns keep going after you quit, up to the provider's session limit.

  • Pliers · an access token

    GitLab

    gitlab.com or self-managed

    Merge requests and issue links work like GitHub's, on your own GitLab host.

    Fewer events: employee triggers don't see failed pipelines, approvals or requested changes.

    foreman gitlab add https://gitlab.example.com

Example run: ENG-123, start to finish

8 of 8 steps work with this belt. Missing tools grey out their steps.

  1. Linear

    Starts from ENG-123, “Login loops after sign-in”. The agent reads the issue and its comments.foreman run issue ENG-123

  2. Workspace

    Workspace osaka runs in a E2B sandbox, on eng-123-login-loop. Provider keys stay on your computer.

  3. Langfuse

    Reads the trace of the failing POST /login: the redirect fires before the session is saved.

  4. MCP

    Hands “add a regression test” to lisbon with start_task, then reads the reply.

  5. Pull request

    Pushes the branch and opens draft PR #42 on GitHub.foreman pr create atlas --draft

  6. CI

    CI fails: Tests, 1 failing. Foreman saw it, so you don't have to refresh.

  7. Back to green

    Auto-fix is off: Home shows CI failed and you press Fix CI in…. Checks pass.

  8. Slack

    Drafts “PR #42 is ready for review” to @maya, the reviewer. It waits for your Send.The agent also posts the fix to #launches.

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.

  1. GitHub
  2. Linear
  3. Slack
  4. 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.

  • Wrench · gh or a token

    GitHub
    Auto-fix CI

    Commit, push and open draft PRs. Merge, or auto-merge when checks pass. Watch CI and reviews. Start from an issue or PR link. Open PRs in GitHub or Graphite.

    A failing CI run waits on Home with Fix CI in… for you to press.

    Auto-fix sends the failing log to the tab you picked: 2 fixes a commit, 5 a PR. Never for review comments.

    Agents in repositories that use it get GH_TOKEN. Turn approvals on to see each push first.

  • Level · an API key

    Linear
    What agents may do

    Agents get no Linear tools. Foreman still reads issues for New workspace.

    Agents can search and read issues, projects and comments.

    Agents can also create and update issues and comment.

    Nothing goes to Linear from an agent.

    They can't create, edit or comment.

    Issue text is written by others, so treat this like any tool that changes things.

    Foreman doesn't change issue status itself.

  • Megaphone · a bot token

    Slack
    What agents may do
    Rule: PR ready → message the reviewer

    Foreman sends your notification rules. Agents can't post.

    Agents may also post to #launches, the channel you allowed.

    Messages to anyone but you wait for your Send.

    This rule has your consent; change any part of it and it asks again.

    Outbound only. Never pings @here or @channel.

  • Power strip · built in

    MCP
    Let agents start workspaces

    Every workspace agent gets foreman-app: its status, its checks, a preview, its own chat history.

    No agent can start a workspace or queue a message.

    Agents can hand tasks to other workspaces in atlas and read the replies. Other repositories are refused.

    MCP servers a repository proposes start only after you approve them.

Example run: ENG-123, start to finish

7 of 7 steps work with this belt. Missing tools grey out their steps.

  1. Linear

    Starts from ENG-123, “Login loops after sign-in”. The agent reads the issue and its comments.foreman run issue ENG-123

  2. Workspace

    Workspace osaka: its own git worktree on eng-123-login-loop.

  3. MCP

    Checks itself with foreman-app. Delegation is off, so it writes the regression test too.

  4. Pull request

    Pushes the branch and opens draft PR #42 on GitHub.foreman pr create atlas --draft

  5. CI

    CI fails: Tests, 1 failing. Foreman saw it, so you don't have to refresh.

  6. Back to green

    Auto-fix is off: Home shows CI failed and you press Fix CI in…. Checks pass.

  7. Slack

    Drafts “PR #42 is ready for review” to @maya, the reviewer. It waits for your Send.

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

  1. GitHub
  2. Linear
  3. Slack
  4. Langfuse
  5. MCP
  6. Sandboxes
  7. 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.