Cy. An AI coworker that works from Slack(neonblue.ai)

Tried something similar with a Slack bot wired to Linear last quarter, team of four. The handoff is where it broke for me: it would open a PR but tag the wrong reviewer and drop half the context from the thread it was summarizing. Does Cy keep the Slack thread linked to whatever it ships, or do you end up re-explaining the task in two places? That second part is what quietly ate my afternoons.

most of my "AI coworker" ended up being a 200-line retry-and-dedupe wrapper around the actual model call

We pushed a redline turnaround from two days to about four hours on a 60-page commercial lease using Spellbook last quarter. The catch nobody mentions: every clause it flags still needs a human to confirm against the actual jurisdiction, and a junior associate caught two hallucinated statute cites that would have been embarrassing in front of the client. Slack-native would help our intake, since half our matter requests already start as DMs from the partners. I just would not let it touch anything that goes out the door without sign-off.

Slack-as-interface means every task gets squeezed into a chat thread, and design work is the worst fit for that : a creative director reviewing layouts needs to point at the third comp's kerning, not type "make it tighter." The handoff you skip by living in Slack is the handoff where the actual feedback happens.

We pulled the same trick for contract intake; routing requests through Slack instead of a separate portal cut the back-and-forth a lot. Last quarter I had Slack threads kick off first-pass NDA redlines, and our turnaround on those dropped from two days to about four hours.

Slack-native is the part everyone copies and the part that bites you: I shipped a bot where every threaded reply fired a webhook, and a coworker @-mentioning it inside a 40-message thread re-sent the whole history as context every time. Show me how Cy handles dedup and thread state before I trust it to "work from Slack," because that plumbing is 80% of the actual product.

Cy looks handy for keeping a client in the loop without context-switching, since most of mine live in Slack anyway. I run three client workspaces at once and the constant tab-flipping eats maybe an hour a day, so anything that answers from inside the channel saves real time.

Hand-rolling this exact thing right now: the hard part is not Slack ingress, it is that "AI coworker" implies persistent memory across threads and the ability to say "I did X" truthfully. A bot that reads Slack and replies is a weekend project; one you trust to file a Linear ticket without you re-checking it is six months of guardrails. Show me the audit log before you show me the demo.

Does Cy post into channels unprompted, or only reply when @-mentioned? Curious how you tuned interruption frequency.

Different client setups would each need their own Cy connected, which gets messy fast. Last month I had three Slack workspaces open for three clients and still missed a handoff because a thread got buried under standups.

Three clients, three Slack workspaces, and I already lose an hour a week just remembering which channel maps to which repo. The pitch I'd want answered: does Cy stay walled off per workspace, or does context from client A ever leak into a reply for client B? I got burned once when a Notion AI summary pulled a competitor's name into the wrong doc. Until billing and data isolation are airtight, I keep separate logins and eat the friction.

We ran Cy's closest cousin last quarter: a Slack bot wired to Claude via the Agents SDK, sitting in our 6-person support channel. The win was not the answers, it was that it read the whole thread history before replying, so people stopped re-explaining context. Ticket triage time dropped from about 40 minutes to 8. The failure mode nobody warns you about: it happily @-mentioned the wrong on-call engineer twice before we scoped its user directory access down.

How does Cy handle a Slack thread where three people give conflicting instructions in the same channel?

We shipped a Slack bot last quarter that could open PRs from a thread. Cute demo, but it filed a migration that dropped a column with data still in it, and I spent a Saturday on the rollback. Now it can draft but a human hits merge. The gap between "works in the thread" and "safe in prod" is where my job still lives, at least for now.

Whats Cy do when a Slack thread has three conflicting instructions from three people? Pick one, ask, or stall?

We cut first-response time on tier-1 tickets from 4 hours to under 10 minutes once the bot started drafting replies from our help docs. The trick was making it flag low-confidence tickets for a human instead of guessing, which kept our CSAT from tanking.

most cy-style tools die the second finance asks who owns the audit trail