Capture
—
Sarah posts "we migrated off express in 2024" in #eng-decisions
→
Halyard captures it as a durable knowledge entry, attributed to Sarah, indexed, retrievable by every agent next time.
#eng-decisionsKnowledge entry · Decision
Integrations · Slack
Halyard for Slack.
Slack is where your team's real knowledge is produced — decisions, tribal wisdom, "ask Sarah" moments. Halyard captures that knowledge as it happens, and routes unknowns back to the right human without breaking anyone's flow.
01 · What Slack becomes
Source. And channel.
Slack plays two roles in Halyard. It's the biggest source of uncaptured knowledge your team produces — and it's the routing channel your agents use when they need a human.
Routing
—
Claude Code asks ask_expert("Who owns the billing service?")
→
Halyard identifies Priya as the right expert (via role + activity signals), DMs her with context, and streams her reply back to the agent.
Team roster#platform-billing
Compound
—
Next week, a different agent asks the same question
→
Halyard surfaces the captured answer from Priya — citation, attribution, and freshness intact. No second ping to a human.
Previous expert replyAuto-captured
02 · Setup
Three clicks, one OAuth.
Slack connection lives on the Halyard workspace — not in every teammate's client. You connect once as an admin; everyone on the team benefits.
1
Sign in to Halyard and open Integrations.
The Slack tile has a "Connect workspace" action. You'll need workspace-admin permissions in Slack.
2
Authorise the Halyard Slack app.
Standard OAuth. Grant read access to the public channels you want indexed, plus the DM/conversation scopes Halyard needs to route ask_expert calls.
3
Configure experts + channels.
Assign roles (engineer, designer, PM, ops, etc.) so Halyard knows who to route which topics to. Pick which channels to index for durable knowledge capture.
03 · What Halyard captures from Slack
The stuff that's not written down elsewhere.
Not every Slack message is knowledge. Halyard uses classification + attribution signals to capture the durable stuff — decisions, justifications, expert answers — and let the noise stay noise.
→
Expert replies to ask_expert
Always captured. Attributed to the responder, linked to the original agent question, indexed against the topic.
→
Decisions + rationale in monitored channels
Classifier flags decision-shaped threads in channels you've marked as "decision-relevant" (#eng-decisions, #gtm-strategy, etc.).
→
Pointer threads — "the answer is here"
When someone replies to a question with a link to a doc, ADR, or PR, Halyard creates a pointer relation so future queries find the source.
→
Not captured
DMs (unless you opt in), private-channel content (unless explicitly added), emoji-only replies, chit-chat channels.
04 · How routing works
Agent asks.
Halyard picks the expert. Slack delivers.
When an agent calls ask_expert, Halyard needs to know three things: who to ask, how to reach them, and how to return the reply to the agent.
agent → halyard: ask_expert("deployment pattern for new services")
halyard picks: @priya (staff-eng, deploy expert, 2 active this hour)
halyard → slack: DM to @priya with agent context + original question
priya → slack: "Fly.io with custom deploy.yaml. See the platform-deploy repo."
halyard captures the reply, attributes it to priya,
streams it back to the agent as a citation-grounded answer.
✓ 3.2 minutes, one DM, one captured knowledge entry
✓ next agent asking gets the answer without pinging priya againTurn Slack into your team's knowledge layer.
Three clicks, one OAuth, and the decisions your team makes in threads become durable for every agent you run.