CAPABILITIES OVERVIEW
What ClaudeAutonomous does
Six core capabilities. Each one is the kind of thing teams usually build themselves over months. We’ve already built them — and they connect.
THE KILLER FEATURE
Group chat where Claude is just another participant
Most AI tools force one human to be the “interface” between the team and the AI. Someone types a question, then relays the answer to a Slack channel. By the time everyone weighs in, three context-switches have happened and key information is lost.
ClaudeAutonomous treats Claude as a first-class member of a chat thread. Multiple people log in, share the same conversation in real time, see Claude’s responses as they stream, contribute their own context. Like Slack or WhatsApp — but with the AI in the conversation, not commented at from outside.
Under the hood: SSE streaming chat history, shared via the user’s web UI on their personal Control node. Artifacts (specs, code, designs) get versioned and synced via Domino replication so everyone is editing the same artifact, not their own copy.
APPLICATION PORTAL
Your team’s homepage, with Claude on standby
Instead of a chat-first UI, ClaudeAutonomous opens to an Application Portal — a dashboard of all your team’s tools. QuickBooks lives there. Your CRM lives there. Your support inbox lives there. The Domino apps you run internally live there.
When you need to actually do something, you click the tool. When you need to ask a question across tools — or just think out loud — Claude is one click away in the corner.
Apps are grouped by department (Sales, Support, Finance, Operations) and by function (CRM, monitoring, accounting). Claude-built and Claude-maintained apps get a distinct badge so you know which ones are AI-generated.
NATURAL-LANGUAGE QUERY
Ask plain English. Get answers from your whole company.
“Show me every customer who opened a support ticket in the last 90 days and also had an invoice issued.” Claude queries your CRM, your support system, and your accounting in one pass, joins the results, and shows them in a table. No SQL. No middleware. No data warehouse.
The integration happens through MCP bridges — the same protocol Claude Desktop uses to talk to GitHub, Asana, or Postgres. Adding a new system means adding one MCP bridge, not rebuilding a data pipeline.
IDENTITY & ACCESS
Every user has a GitHub PAT. Every PAT scopes what they can see.
Users authenticate with their GitHub identity. Their Personal Access Token determines which repositories Claude can read for them, which it can push commits to, and which it can’t touch. Same model your developers already use.
For non-developers, the PAT is invisible — they just see the apps and chats they have access to. The PAT is the access enforcement mechanism, not a feature they have to configure.
FLEET ARCHITECTURE
One Control node per user. Your data stays under your roof.
Each user gets their own Control node — a Mac Mini, an EC2 instance, or whatever platform you prefer — running Claude Desktop, an embedded Domino server for artifact replication, and an MCP bridge layer. Plus a Managed node for testing and prototyping.
Nothing is in a vendor’s cloud you don’t control. Sensitive customer data never leaves your network unless you explicitly opt in. Compliance teams can audit exactly what’s where.
Today: Mac Mini fleet plus a central HA Postgres for cross-fleet coordination. Tomorrow: AWS-compatible deployment for production scale.
MCP BRIDGES
If it has an API, we can give Claude access to it
MCP (Model Context Protocol) is how Claude reaches outside its chat window. We’ve built bridges to GitHub, Postgres, SSH operations management, Mac/Linux filesystem control, HCL Domino, FortiNet networking, and dozens more.
Each bridge is versioned, backed up, and reviewable. When you want a new integration, you write the bridge once — in Python, usually under 200 lines — and every node in the fleet gets it. No vendor approval needed.
DATA LAYER
Domino for replication, Claude for everything else
Each Control node runs a local Domino server. Why Domino? Because Notes/Domino has done multi-master replication of structured data better than any other database for thirty years.
Artifacts — specs, designs, agreed-upon decisions, code review threads — live in Domino databases and replicate between nodes. When you’re collaborating with the team, you’re all editing the same data, eventually consistent.
If your team already runs Notes/Domino, ClaudeAutonomous plugs in. If you don’t, it brings Domino along quietly as infrastructure — you never see it as a user.