Overview
This is a curated list of real rousseau-agent deployments. It exists so newcomers can see representative shapes: solo operators, small teams, community bots, and airgapped shops.
Deployment shapes we know exist
One developer, one workstation. WhatsApp transport pointed at their own number. claudecli inheriting Claude Code auth. Uses rousseau chat at the desk, WhatsApp on the go. Cron jobs for nightly git summaries. Session store on the local disk, backed up nightly.
5–10 engineers, one shared daemon per project. Slack Socket Mode in an on-call channel, Discord in a community channel, WhatsApp for individual pair-programming sessions. Provider: Bedrock via a scoped AWS profile per project. Rootless Podman under systemd Quadlet.
Public Discord server for an OSS project. Answers doc questions with citations. Provider: anthropic with prompt-cache markers. agent.approver.mode: pattern with only read/grep. Cost is a rounding error thanks to caching.
A regulated shop with strict egress rules. No calls leave the internal network. Provider: ollama on an internal GPU box, llama3.1:70b-instruct. Transport: self-hosted Matrix (Synapse). No public WebSocket transports. Tool-use quality noticeably lower than Anthropic but acceptable for their workflow.
Wanted
If you're running rousseau in production and want to be added, we specifically want to hear:
- Your provider + transport combination.
- Rough scale (messages/day, sessions/week).
- Whether you're on bare-metal, Podman, Kubernetes, or something else.
- One thing that surprised you (good or bad).
Open a PR with a short markdown block; no company logos, no marketing copy.
Related pages
- Community: Contributing
- Community: Overview
- Recipes — the recipe catalogue mirrors what showcased users are doing.
- Deployment