Explore ty-slack sidecar for managing TaskYou from Slack (task #3723)#545
Open
bborn wants to merge 1 commit into
Open
Explore ty-slack sidecar for managing TaskYou from Slack (task #3723)#545bborn wants to merge 1 commit into
bborn wants to merge 1 commit into
Conversation
Answers two questions from the Slack screenshot in task #3723: 1. Did we already build this? No. The only prior "Slack" work (PR #433, task #1172) was marketing copy, not an integration. Closest precedent is the ty-email sidecar (#371/#385); PR #402 circled the remote-MCP idea. 2. Does a Slack sidecar make sense? Yes — and ~90% of it already exists. Documents two patterns (chat-control sidecar vs hosted remote MCP), recommends building ty-slack as a near-clone of ty-email by reusing the existing CLI bridge, LLM classifier, ty serve HTTP API, and the events/hooks push mechanism. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Task #3723 asked two questions about the attached Slack screenshot (Claude-in-Slack can't reach the TaskYou agents server):
This PR adds a written exploration/proposal answering both:
docs/proposals/ty-slack-sidecar.md.Answers
Did we build this before? No. The only prior "Slack" work was marketing copy (PR #433 / task #1172), not an integration. The direct precedent is the
ty-emailsidecar (#371/#385); PR #402 (closed) circled the harder "remote MCP" idea. No open issue/PR exists for a Slack control surface.Does it make sense? Yes — and ~90% already exists. The proposal separates two readings:
ty-slacksidecar (recommended): a near-clone ofty-email. Chat -> LLM intent classify -> drivetyCLI /ty serveAPI -> reply in-thread -> push notifications via the existingtask.blocked/task.completedevent hooks. Reuses the existing CLI bridge, classifier, HTTP API, and events system; the only new code is a Slack adapter + thread<->task state.taskyou_*tools is a separate hosting/auth project. Recommended as a deferred follow-up.The "ping me in Slack when a task is blocked/done" half can ship immediately as a documented event hook -> Slack webhook, independent of the full sidecar.
Files changed
docs/proposals/ty-slack-sidecar.md(new)Note on scope
This task was framed as an exploration ("would it make sense... did we already have a PR?"), so the deliverable is a recommendation doc rather than an implementation. Open questions for Bruno (single shared bot vs per-user, Socket Mode vs Events API, whether to also pursue Pattern B) are listed at the end of the doc.
🤖 Generated with Claude Code