Solutions

Projects & sprints

The week in a channel, for whoever was out.

#ml-internalprivate channel2 tool calls

A week of a channel for whoever was out, read from the record rather than from whoever remembers it best: workstreams, who is on each, the decisions, each linked. The same read is what a scheduled digest runs on.

ml-internal

Mei9:05 AM

@attest_tag what happened in this channel this week? I was out

attest_tagApp9:06 AM

  • read_channel_history · last 7 days · 2 pages · 71 messages
  • read_thread · 4 threads

Recap of #ml-internal, 6–12 Sep:

  • Lookup enhancement (Priya): testing and bugfixes, pagination for the unified table, backward-compat checks; a new model under evaluation for split
  • Release (Dan): tracing switched on for the document pipeline, model updates, the eval API at v0, split models standardised
  • Cost: a concern flagged Wednesday about extraction cost per document — a follow-up thread, no decision yet

Two decisions, both linked: the eval API stays internal for now (Tue); the standardised split model ships next release (Thu).

google/gemini-flash9.9k in560 out$0.0052Configure

Names, figures, repositories and customers are changed; token counts and cost are illustrative. The ask, and the shape of the answer, are as they were.

How the turn went

The week and its threads, grouped by workstream, on a schedule if you like.

  1. 01

    Read the week, then the threads

    The channel first, then the threads the interesting messages sit in. Slack is rebuilt on every turn, so an edited message is read as it is now.

  2. 02

    Group by workstream, name the people

    Not a chronological list. The grouping is the model’s; the names and the links are the record’s.

  3. 03

    The same read, on a schedule

    “Every Friday at 4pm post a recap of this channel” is one sentence and a routine.

What it needs

The setup, in the console.

Connection
None. Reading a channel or a thread the bot is in is a native tool, with no credential beyond the bot's own.
Scope
Any channel it is in. A private channel is readable to a member asking; it checks.
Long weeks
A busy channel is read in pages, and a long thread is windowed with a running summary rather than truncated.

What it will not do

Enforced outside the model.

  • It reads with its own token, so before touching any conversation that is not the current one and not public, it checks the asker's own membership. It cannot be used as a periscope into a channel you were not invited to.

  • It summarises what was said; a decision it did not find is reported as not found, not inferred.

Try it

Say it in a channel it is in.

The sentence as it was typed. It works in any channel the bot has been invited to that carries the connection above — no command syntax, no form, and follow-ups in the thread need no mention.

@attest_tag what happened in this channel this week? I was out

  • Slack
  • read_channel_history
  • read_thread

Bring the channel this would live in.

Sign up, connect the service above in one channel, and type this sentence yourself — or run the same binary on your own infrastructure.

All solutions