Fleet a side project atPostHog
All packs

Slack

Your own message, reaction, or mention in Slack starts a T3 thread about it.

Add to your Fleet

How it works

  1. Your Slack message or reaction
  2. Your Slack app
  3. T3 thread
  4. Link in Slack

Workflows

  • Start a thread from Slack

    Off until you turn it on

    Your own Slack message or reaction with your trigger emoji (default :t3code:), or a mention of your Slack app starts a T3 thread, and Slack shows you its link. With the Context library pack on, your :brain: reaction saves the thread to your notes.

    Read before you turn it on

    Your Slack messages and the threads they belong to become agent prompts. Only your own messages, reactions, and mentions start a thread.

What it costs

You need your own Slack app, which you make from a manifest in a few minutes. One small process stays connected to Slack.

Know before you turn it on

Your Slack messages and the threads they belong to become agent prompts. Only your own messages, reactions, and mentions start a thread, and the prompt treats the rest of the Slack thread as data.

Settings4 settings that your agent asks about
  • slack.userIdWhat is your Slack member ID, so only your own messages start threads? In Slack, open your profile, then More, then Copy member ID.
  • slack.emojiWhich Slack emoji starts a thread? Give its name, such as eye or +1.Default: t3code
  • slack.captureEmojiWhich Slack emoji saves a message and its thread to your context library? Give its name, such as brain. It works while the Context library pack is on.Default: brain
  • slack.nodesWhich nodes start the threads that Slack asks for, as SSH names separated by spaces, such as devbox-1 devbox-2? Fleet takes them in turn. Leave it empty to start them on the hub, or on a box while Boxes is on.

Add Slack to your Fleet

Paste this prompt into a T3 Code thread on a machine that runs Fleet.

Your install prompt

Add this Fleet pack to my setup with me: Slack.

Fleet already runs on this machine. Ask me each choice with your question tool, and run every command yourself.

1. Run `fleet update`, so this machine has the newest engine and packs. Then run `fleet packs`, and leave out each pack that is already on.
2. Read the setup note of each pack. Ask me what it asks, and collect the flags that it names. Where a note names "the setup command" or "the command in step 9", use the `fleet packs` command of this prompt. Do not run a step that a note puts after that command yet.
   - Slack: ~/.local/share/fleet/engine/packs/slack/SETUP.md
3. Turn the packs on with one command, and add the flags that the notes name:
   fleet packs --add slack
4. Do the steps that each note puts after the command.
5. Run `fleet doctor`, and explain each line. Do each `To do:` line with me, and say what a sign-in is for before it opens.
6. My other machines take the change at their next `fleet update`. To give it to one now, run `fleet update` there.
Open in T3 Code

Add more packs in one prompt