08:55ClarissaEng manager
Opens Slack before standup.
Ambient Samosa already surfaced the stale auth-migration thread — 14h unanswered — so the standup starts with a decision, not a scavenger hunt.
● ambient · stale thread in #auth-migration · 14h
● live in your channels
The AI teammate in the room where work happens.
One shared agent per Slack channel. MCP connectors, Azure DevOps workflows, and a personal assistant in DM, the browser, or Telegram — on your infra, on any model.
samosa — demoing itself · take the keyboard anytime
●memory·wrote to MEMORY.md · "session expiry: always add 5s leeway"●ambient·surfaced stale thread in #launch · 18h unanswered●schedule·weekday 9am · top AI news → DM @maya●mcp·github.create_issue · connected via Connectors●channel·#engineering · shared agent picked up mid-thread●azure·PR #4421 review ready · 3 comments, 1 blocker●telegram·inbound DM · same personal assistant●media·generate_image · team-gated spend ok●inbox·digest ready · 4 mentions still need you●watch·PR opened on a watched repo · reviewed without being asked●react·:bug: on a message · Bug #4120 filed, link posted●docs·spec.pdf indexed · searchable in #platform only●skills·#data installed the release runbook #platform published●budget·#support at 82% of today's cap · still under
Slack ·Web ·Telegram ·MCP ·GitHub ·Azure DevOps ·DeepSeek ·OpenAI ·Gemini ·Anthropic ·Media gen ·Postgres ·
cinematic demos
Stick with the shot. Scroll to cut.
Five sticky frames. Each one holds while you scroll — like a product film, without leaving the page.
01 · channel
Everyone talks to the same agent.
Sessions key on the channel, not the user. Mid-thread pickup, attribution, one MEMORY.md the whole room trusts.
maya shipping pilot invites tonight
dev pricing settled — see pinned
ana @samosa what did I miss?
samosa
Three decisions, two blockers. Short version: …
scroll-driven · shot 01
02 · tools
You see every step it takes.
Built-ins, MCP connectors, Azure — the breathing chip shows the move. No spinner theater while you wait.
searching channel history…
scroll-driven · shot 02
03 · personal
Hand it work. Walk away.
Schedule, remind, or delegate a full agent turn from Slack DM, the browser, or Telegram. Results land in Slack DM or web chat when it's done.
0 9 * * 1-5top AI news → DM
once · nowresearch pricing → ping me
donebrief ready in your Slack DM
scroll-driven · shot 03
04 · triggers
Or start it from anything that can POST.
Give an agent a webhook URL and a failed build, a new ticket, a form or a phone shortcut can run it. What the caller sends becomes the agent's input, so it reports on what actually happened.
POST/hooks/••••• ← your CI, on failure
202queued
→“test_login broke on the payments migration”
the URL is the key · revoke by deleting the agentscroll-driven · shot 04
05 · memory
Decisions stick without a wiki.
After each turn the agent curates MEMORY.md. Skills write themselves after complex jobs — and can call MCP tools when connectors are on.
MEMORY.md
- · session expiry: always add 5s leeway (auth/session.py)
- · pricing: Starter free · Team $12/seat after pilot
- · Priya owns pricing-page copy by Friday
scroll-driven · shot 05
anatomy · one wednesday
A channel-native teammate, from 08:55 to 17:30.
Not a company brain over every SaaS ACL. One shared agent in the rooms where work already happens — with MCP, Azure, and ambient when you need them. Scroll the day.
08:55 → 17:30 · scroll ↓
10:15ThereseIC
Hits a connection-pool bug mid-PR.
@samosa in #engineering. Shared agent answers from channel history + MEMORY.md: two past fixes, the 5s leeway pattern, and who last touched the pool.
● channel · “what did we decide about pool timeouts?”
12:30AdekunlePM
Hands off a research job and walks into lunch.
“Research competitor pricing and open a GitHub issue with the brief.” Samosa runs in the background — web search plus an MCP GitHub tool from Connectors — then DMs him when it's done.
● mcp · github.create_issue · after research
15:00ApoorvCTO
Asks for the board update from the channel.
One @mention. Samosa pulls decisions, blockers, and owners from the week’s threads — attributed, not a generic summary that invents consensus.
● memory · week’s decisions · with @attribution
16:15ClarissaEng manager
Reviews a PR from Slack.
@samosa review PR #4421. Worker clones, reviews, comments in Azure — human still merges. The thread stays the source of truth.
● azure · PR #4421 review · 3 comments ready
17:30KabirDesigner
Gets the inbox digest on the way out.
Weekday DM: four mentions still need him, nothing already resolved. He answers two, closes the laptop. Channel memory keeps tomorrow warm.
● inbox · 4 mentions waiting · 0 already handled
video guides
Watch it like a cut. Ship it in the channel.
Short product guides — cinematic sequences today, swap in AI-generated MP4s under public/guides/ when you have them. Channel-native teammate with MCP, Azure, Telegram, and media — not a company-wide ACL brain.
guide · cinematic0:42
01Invite @samosa to #engineering
02Someone asks what they missed
03Shared agent answers with attribution
04MEMORY.md updates after the turn
Drop an MP4 at /guides/channel-agent.mp4 to replace this sequence with a real AI-generated cut.
Invite Samosa, @mention it, watch the whole room pick up mid-thread with one memory.sequence
surfaces
One teammate, everywhere you work
In your Slack channels
@mention Samosa in a channel and it joins the conversation — shared by the whole team, with MCP tools, Azure DevOps, and channel memory following up with the right person.
In the web chat & Telegram
Sign in with Slack for `/chat`, or talk on Telegram. Same personal assistant: search, schedule, delegate, and (when your team grants it) generate images or video.
In your morning inbox
Opt in and Samosa DMs you a weekday digest of what's waiting on you — the @-mentions you haven't answered, minus the threads someone else already handled.
standing orders
The work that happens without anyone asking
Watch a repo, review every PR
Say “watch this repo” once. Every pull request opened there gets read in full — the whole diff, not a truncated window — and comes back as inline comments on the PR, with the channel that asked kept in the loop. It never approves, never merges, and never pushes to a protected branch.
React instead of typing
No @mention needed. React with `:bug:` and it files an Azure DevOps bug from that message. `:pushpin:` saves the fact to channel memory. `:thread:` recaps the thread — decisions and open action items.
A searchable library per channel
Drop a PDF, spec, CSV or spreadsheet in the channel and it's chunked, embedded and searchable from then on. Scoped to that channel, so a document shared in #legal never surfaces in #support.
Skills travel between channels
A channel writes its own playbooks after complex jobs. Publish one to the workspace and any other channel can browse and install it — the runbook #platform worked out becomes the one #data follows, without a wiki page nobody updates.
governance
Governed by default, not by roadmap
Tools granted per team
Risky tools and media generation are grants, not defaults. Put someone in a team and they get exactly that team's tools — enforced when the agent is offered the tool and again when it tries to run it, so a model can't be talked into one it was never given.
Spend capped per channel
Daily and monthly token caps live in the channel's own BUDGET.md, overriding the global limit. Usage survives restarts, and once a cap is hit the agent declines until the window rolls over. No surprise invoice from one busy channel.
An audit trail that reads nothing
Every turn is recorded as who asked, which tools ran, and what it cost — with the message text deliberately never stored. Admins get a coarse intent label instead, so oversight never turns into reading your team's messages.
how it works
Get started in three steps
- 01
Add Samosa to Slack
Install the Slack app, invite it to a channel, and @mention it. That channel now has its own shared agent, memory, and skills.
- 02
Connect tools
In the admin panel, add MCP connectors (or Connect GitHub). Wire Azure DevOps if you review PRs from Slack. Grant teams the tools they need.
- 03
Open every surface
Sign in to `/chat`, optionally start the Telegram gateway, and opt in to the weekday inbox digest from a Slack DM.
Self-hosting for your own team? docs/ONBOARDING.md walks through the Slack app, web sign-in, and how a second workspace gets its own instance.