open source · claude code skill

strato.

A control tower for one person. Strato routes what reaches you in Slack, in Linear or in a tool you connect, surfaces only what is for you, opens one Claude Code session per topic and prepares the exact action. Nothing goes out without your go.

01The circuit

One message, from the Slack thread to your posted reply, in five steps.

  1. 01Slack

    Strato listens to your Slack and keeps only what is for you: mentions, your team group, DMs, watched channels, replies in your threads. The rest goes to a digest.

  2. 02Topic

    The problem becomes a topic with a letter, B here. A topic can group several threads and a ticket.

  3. 03Session

    Each topic gets its own background Claude Code session. It reads the thread and investigates with your access, without posting anything.

  4. 04Card

    The session prepares the card: the request, its proposal and the exact action, here a draft reply.

  5. 05Go

    You read the card on the board and say go. The reply goes out in the thread, as you. Nothing is posted or written to production before that.

02The board

A local page on 127.0.0.1. Four blocks, one lamp each: at a glance you see what is waiting on you, what moved, what is running and what is waiting on someone else.

strato board

Waiting on you2

a draft or an action to approve, a decision, a blocked session

Just a go

B

CI red on the 2.4 release

Bob · #platform-requests · draft ready

Hi Bob, the staging certificate expired overnight. I'm renewing it and rerunning CI, it should be green within the hour.

A decision

A

Slow Docker build

Keep the build cache on the shared runner?

To review1

the thread moved after the card

C

Staging access for Dana

Dana · DM · new message after the card

At work1

the session or its sub-agents are running

D

Migration to Postgres 17

2 sub-agents

Waiting on someone1

a third party has to answer, or a teammate took the topic

E

Carol's question on feature flags

waiting on Carol since yesterday

Also built in

Shadow mode

On day one, sessions prepare real cards but nothing goes out. setup --live once the drafts are ones you would send.

The digest

What is not aimed at you is set aside, grouped by channel, and summed up when you ask "what's new".

One-click update

The version sits in the board’s top bar. When a new one is out, one click installs it and restarts the board; the previous one stays next to it to roll back.

Revalidated cards

If the thread moves after the card, the card goes to review. The session rereads the thread and brings the card back to the real state, without sending anything.

Real time, or close

With Socket Mode, a message arrives within a second. Without it, Strato polls Slack every minute.

All the way to production

A topic’s GitLab merge requests are followed to production, with what blocks them. Linear tickets are attached to the topic.

  • Terminal in the board (ttyd)
  • iTerm2 side panel and dive
  • ⌘K: find a topic or ask the master
  • Later: pause a topic
  • Full review over 24 h, 3 days or 2 weeks

03Not a developer?

Strato is not only for people who write code. You tell it your job once, and the work sessions behave accordingly.

Your jobRoleWhat a session does with a request
Customer supportsupportFinds what the customer needs to hear, drafts the answer in their tone, and prepares any escalation to engineering as a separate step.
OperationsoperationsFollows the runbook, writes every production step as its own action, and drafts the incident update.
Account management, salesaccount-managerGathers the client’s history, drafts the reply, sets a reminder for every promise, and prepares CRM changes for your go.
Team lead, managermanagerFrames each decision as options with a recommendation, and proposes who to delegate to.
Software developerdeveloperInvestigates in the code, implements tickets up to a merge request. This is the default.

04Connect your tools

Slack and Linear are built in. Any other tool connects through a provider you write, loaded from disk without recompiling Strato.

Built in

Slack

In
mentions, your team group, DMs, watched channels, replies in your threads
Out, on your go
your reply in the thread, the ✅ reaction, Undo for 30 s

Linear

In
your notifications: an issue assigned to you, a comment that mentions you
Out, on your go
a comment, a status change, an assignment, Undo for 30 s

GitLab

In
a topic’s merge requests, followed to production with what blocks them
Read only, on the board

Connecting

strato setup --connect, in your own terminal: a token never goes through a conversation. Secrets go to a file readable by you only.

$ strato setup --connect slack

Slack

  1. your own app, created from the manifest
  2. a user token you already have
  3. your team’s shared app, over OAuth with PKCE: you approve in your browser, no token to handle

Linear

  1. a personal API key, the quickest
  2. OAuth with PKCE: nothing pasted, a token renewed every day

Write your provider

A ticket tracker, a CRM, a support desk: a TypeScript module, or a program in any language speaking a small JSON-RPC protocol.

$ strato provider new ticketsa scaffold that works as is

$ strato provider test ./ticketsthe offline conformance harness

$ strato provider trust ticketsyour trust, typed in your own terminal

Two examples written by outside authors from the guide alone: GitHub (a TypeScript module) and email (a Python program over IMAP and SMTP).

An external provider runs with your privileges: your files and your network, like any command-line tool. Strato loads it only once you trusted its folder as it is; a change to the folder needs a new trust. Its writes go through the same go, and nothing goes out in shadow mode.

05Install

Open Claude Code in the project that will be your workspace, paste this prompt, and follow along.

claude ›
Install Strato for me: an open source Claude Code skill by Hugo Blanc that acts as a personal control tower for Slack, Linear and my other tools (https://github.com/hugoblanc/strato).

The folder you are running in becomes Strato's workspace: each topic's session will run here, with its CLAUDE.md and MCP servers. Run every strato command from this folder.

1. The binary: if the `strato` command already exists, run `strato update`. Otherwise, on macOS or Linux, run `curl -fsSL https://raw.githubusercontent.com/hugoblanc/strato/main/install.sh | sh`: it downloads the binary for my platform, checks its SHA-256, installs it in ~/.local/bin and writes the skill to ~/.claude/skills/strato. If ~/.local/bin is not in my PATH, give me the line to add. On Windows, follow the Windows section of the README.
2. The setup: read the "Setup" section of ~/.claude/skills/strato/SKILL.md and run it with me to the end. The files it mentions (SETUP.md, examples/) are in the GitHub repository. In order: prerequisites and the Slack app, automatic detection, an interview about what it could not find, review of config.json and local.md before writing them, a rehearsal on the last 24 hours, then start in shadow mode.

Rules: never ask me to paste my Slack token in the conversation (I will enter it in my terminal), post nothing on Slack, and do not turn on workers.skipPermissions unless I explicitly ask.

What the prompt does

  1. 01The binaryOne executable, no Bun or Node, checked against its SHA-256. Or strato update if it is already there.
  2. 02PrerequisitesClaude Code and a Slack connection: your own app, a token you already have, or your team’s app. You type the token in your terminal, never in the chat.
  3. 03DetectionYour Slack identity, your team, your most active channels, your repositories and tracker, found without asking you anything.
  4. 04The interviewOnly what detection could not find. You review config.json and local.md before they are written.
  5. 05RehearsalWhat Strato would have raised over the last 24 hours, to tune the filters. Nothing is opened or posted.
  6. 06Shadow modeSessions prepare real cards but nothing goes out, until setup --live.

06What the agent will ask you

  • your job and what you are responsible for
  • your team and its Slack group
  • who owns what around you
  • what must never go out without your go
  • the channels to watch and the bots to ignore
  • your tracker and repositories
  • the sessions’ permissions
  • the language and tone of your drafts

Answers go into .strato/config.json and .strato/local.md, which you review before they are written. It takes about twenty minutes.

07What you need

Machine
macOS or Linux (x64 or arm64). Windows on a best-effort basis.
Software
Claude Code with background sessions (claude --bg). Nothing else: Strato is a standalone binary.
Slack
a connection, in one of three ways: your own app created from the manifest in the repo, a user token (xoxp-…) you already have, or your team’s shared app over OAuth with PKCE. Your Slack admin may have to approve the app. Socket Mode (real time) is optional.
Optional
a Linear API key (or an OAuth application) to read and act on tickets, glab for GitLab merge requests, ttyd for the in-board terminal, iTerm2 for the side panel.

08Before you install

Your identityStrato acts with your access: your Slack token, and your Linear key if you connect it. It reads what you read and writes as you, on your click.
The boardlistens on 127.0.0.1 only, without authentication. Do not expose the port, and do not install Strato on a shared machine.
Sessionsrun with your MCP servers. They read without asking, but no write tool is pre-approved. Running without permission prompts (skipPermissions) is off by default.
External providersrun with your privileges: your files, your network. Strato loads only the ones config.json names, once you trusted their folder (strato provider trust, in your own terminal). Their writes go through the same go.
Incoming messagesare treated as data, never as instructions. This reduces prompt injection risk; it does not remove it.

Updating

The board shows the version and an "Update" button as soon as a new release is out, or run strato update in a terminal. The previous version stays next to it to roll back (strato update --rollback).

Nothing goes out without your go.

Paste the prompt, answer the interview, read your first cards in shadow mode.

Read the code ↗