Skip to content

Explore ty-slack sidecar for managing TaskYou from Slack (task #3723) - #545

Closed
bborn wants to merge 2 commits into
mainfrom
task/3723-explore-taskyou-mcp-sidecar-extension-fo
Closed

Explore ty-slack sidecar for managing TaskYou from Slack (task #3723)#545
bborn wants to merge 2 commits into
mainfrom
task/3723-explore-taskyou-mcp-sidecar-extension-fo

Conversation

@bborn

@bborn bborn commented May 29, 2026

Copy link
Copy Markdown
Owner

Summary

Task #3723 asked two questions about the attached Slack screenshot (Claude-in-Slack can't reach the TaskYou agents server):

  1. Would a TaskYou MCP sidecar for Slack make sense?
  2. Did we already have a PR for this or something related?

This PR adds a written exploration/proposal answering both: docs/proposals/ty-slack-sidecar.md.

Answers

Did we build this before? No Slack — but we built the exact pattern twice.

Does it make sense? Yes — low-risk, mostly copy-adapt-configure. Two readings:

  • Pattern A — chat -> TaskYou control bridge (recommended): analog of both ty-email and the Linear poller. Recommended home is a taskyou-os module (modules/slack/, mirroring modules/linear/, SLACK_ENABLED=true), tailing notifications.jsonl for push; extensions/ty-slack Go sidecar is the fallback template.
  • Pattern B — hosted/remote MCP endpoint (what the screenshot depicts): TaskYou's MCP server is stdio-only/not network-reachable; exposing taskyou_* to cloud Claude-in-Slack is a separate hosting/auth project (builds on PR Review Cloudflare Code Mode MCP for TaskYou #402 + the taskyou-os credential-proxy design). Deferred.

The "ping me in Slack when a task blocks/finishes" half can ship immediately as a task.blocked/task.completed hook (or a tail of notifications.jsonl) -> Slack webhook.

Files changed

  • docs/proposals/ty-slack-sidecar.md (new)

Note on scope

Framed as an exploration, so the deliverable is a recommendation doc rather than an implementation. Open questions for Bruno (module vs standalone sidecar, shared bot vs per-user, Socket Mode vs Events API, whether to also pursue Pattern B) are at the end of the doc.

🤖 Generated with Claude Code

bborn and others added 2 commits May 29, 2026 09:25
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>
Bruno pointed at github.com/taskyou/taskyou-os. It's the remote-management
layer for TaskYou and already contains the closest precedent: a Linear
poller module (modules/linear/linear-poll.mjs) that bridges Linear @agent
comments -> ty create/execute -> posts diffs back. So we've now built this
exact channel-bridge pattern twice (ty-email + Linear poller).

Updated the proposal to:
- recommend building Slack as a taskyou-os module (modules/slack, mirroring
  modules/linear), enabled via SLACK_ENABLED, tailing notifications.jsonl
  for push; ty-email Go sidecar kept as the fallback template
- add a "where should it live" comparison (taskyou-os module vs extension)
- note notifications.jsonl + the GM as the existing push substrate
- link Pattern B (remote MCP) to the taskyou-os credential-proxy design

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@bborn

bborn commented Jun 8, 2026

Copy link
Copy Markdown
Owner Author

Superseded by taskyou/taskyou-os#33 — the recommended home for the Slack integration is a modules/slack/ module in taskyou-os (mirroring modules/linear/), so the design doc now lives there. Closing this in favor of that PR.

@bborn bborn closed this Jun 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant