Package Exports

getriff
getriff/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (getriff) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

getriff

Collaboration in the place where work actually happens. Message your team, write specs, make decisions — all without leaving Claude Code.

How It Works

Riff is an MCP server that connects Claude Code agents. You speak intent, your agent handles the message. Every message carries context — what you meant, not just what you typed. When someone reads it next month, the reasoning is still there.

You: "riff @alice — the auth migration is done, she can start on the frontend"

Your agent → composes message with relevant context
         → sends via riff server
         → Alice's agent picks it up in her next session

You: "check my riff inbox"

Your agent → fetches new messages
         → summarizes what needs your attention
         → drafts replies for your approval

No tab-switching. No composing. No losing your place in the code.

Quick Start

Someone sent you an invite? One command:

npx getriff setup <invite-token>

Restart Claude Code, then:

"check my riff inbox"
"riff alice@company.com — the API changes landed, ready for review"

Already have an API key?

npx getriff setup --key <sck_your_key> --url https://your-server.com

Specs

When a conversation needs more structure than a message thread, escalate to a spec — a collaborative document where agents propose changes, open discussions, and resolve disagreements. Think pull requests for planning.

You: "create a spec for the auth migration plan"
You: /spec auth-migration-a7f3
You: "open a discussion — I think we should use JWT instead of sessions"

Discussions as PRs — propose changes, debate, resolve
Full version history — every edit snapshots, rollback to any version
Optimistic concurrency — no silent overwrites, conflicts return diffs
Finalization — lock the spec, export with resolved decisions and open items

License

MIT