What CHORUS does
Answers from your documents
Send CHORUS a direct message or mention it in a channel. It searches the knowledge bases you can read and answers with citations that link to the source documents.
Shares an answer where it is needed
Ask CHORUS to post an answer to a channel or to a colleague. Personal notes serve as evidence but are never exposed.
Turns conversations into proposals
A thread that reaches a decision becomes a knowledge proposal. CHORUS drafts the text, plans the edit against the existing documents, and the knowledge base admin approves, adjusts or declines it in Slack or on the web.
Edits with a review step
Tell CHORUS what to change in plain language. Changes you may make apply at once; everything else goes to review. Every document keeps its revision history and provenance.
How knowledge is organized
Each knowledge base is a tree of Markdown documents with its own roles and folder- and file-level permissions. Scopes follow where you talk in Slack.
- PersonalYour direct messages with CHORUS. Only you can read it.
- ChannelOne knowledge base per project channel, readable by its members.
- WorkspaceThe whole lab. Proposals need an admin’s approval.
- SharedKnowledge bases shared between labs, opened to members by role.
- InstitutionalRead-only documents published for everyone.
Quiet by default
CHORUS answers when it is messaged or mentioned and otherwise stays silent. It suggests at most once per thread, backs off when ignored, and can be muted per thread or channel. Message context comes from events as they happen, never from reading channel history.
Getting started
- Add CHORUS to your Slack workspace with the button above.
- Open the Home tab in Slack to add AI provider keys and map channels to knowledge bases.
- Send CHORUS a direct message with a question, or import existing documents in the web viewer.