CREW Every developer has an AI agent now. None of them talk to each other.
Your team's AI agents, working as one crew.
CREW AI puts everyone's agent, Claude Code or Codex, into your Telegram group. They read the same chat, share one memory and know what the others are doing. When code is needed, an agent offers it, a teammate taps Yes, and it's built in your own GitHub. A human merges.
src/auth/session.ts.src/auth/session.tsA human reviews and merges on GitHub.
What goes wrong when every agent works alone.
And nobody wants an agent with access to their laptop talking to the whole team.
Duplicate work
Two agents fix the same bug and open conflicting PRs, because neither knows the other exists.
Stale context
Your Claude doesn't know what your teammate's Codex learned an hour ago. You copy context around by hand.
Laptop access
A local agent can read SSH keys, .env files and every other project. One prompt injection and it leaks.
One group chat, everyone's agent, safe by design.
Multiplayer
Many people's agents in one chat. They share the same team memory and declare file leases, so they don't step on each other.
Real security design
A sandbox per task, a read-only agent job, humans merge, and a server-side lock on every deploy. See the layers.
Merged work can get paid
Put a bounty on an issue. It's held in escrow and paid when a human merges the fix. Agent economy.
Talk as usual. Say yes when it matters.
CREW AI coordinates. Your GitHub runs the agents. Your team stays in control.
Your team talks
Keep chatting in your Telegram group as usual. Nothing new to learn.
Agents answer live
Each person's agent, Claude Code or Codex on their own subscription or API key, reads the whole chat and answers when mentioned, streaming as it writes.
It offers, you decide
When something needs code, the agent replies with ▶️ Yes, do it / ✖️ No. Nothing starts until a teammate with GitHub write access taps Yes.
Sandbox codes
A fresh, disposable sandbox in your team's own GitHub Actions does the work, then opens a pull request.
Human merges
Someone reviews and merges on GitHub. Agents can't push to your branches, change .github/, merge or deploy on their own.
Deploy from Telegram, with a person in the loop.
Agents write code and propose it. People decide what gets merged and deployed.
| AI agent | Your teammates (in Telegram) | CREW AI bot | |
|---|---|---|---|
| Write code | Yes, in a throwaway sandbox, on its own branch | – | – |
| Open a pull request | Yes | – | Opens it for the agent if needed |
| Merge | Never | Yes, on GitHub | Never |
| Deploy to dev/staging | Can't start it | Tap 🚀 Deploy | Runs your deploy script after the tap, or after a human merge if auto is on |
| Deploy to production | Never | Never from chat | Never (only by hand on your server) |
More than a coding bot in the corner.
Every agent in the group sees the same conversation, the same notes and the same timeline of what the crew did.
Answers in the chat
Mention an agent and it answers live, streaming as it writes. It has read the whole thread, so you don't repeat yourself.
Offer, then Yes
When code is needed the agent offers the work. A teammate with write access taps ▶️ Yes, do it, or ✖️ No.
Shared memory
Agents propose what they learned. A teammate taps Keep before any agent relies on it. Manage it with /memory and /remember. Anything that looks like a secret is refused.
Reads the web
Agents can search and read pages. CREW AI fetches them, so the sandbox stays locked down.
Deploys to your servers
Tap 🚀 after a merge, or let it auto-deploy, using deploy scripts already in your repo. Production is never deployable from chat.
Binance Agent OS
Connect a read-only Binance key with /binance. Agents see live prices and balances, and trade on testnet only. More
Claude Code or Codex, on your own plan.
Each teammate brings their own agent, on their own Claude or ChatGPT subscription or an API key. It stays theirs. Every agent shares one chat, one memory and one set of file leases.
We protect the code and the machine, not just the messages.
Every layer assumes the one before it can fail. Read exactly what we can and can't see.
Agents offer, never start alone
No code is written until a teammate with GitHub write access taps Yes on the offer.
Sandbox per task
A fresh GitHub-hosted VM with only the repo inside. No home folder, no keys, no other projects. Outbound traffic blocked except an allowlist.
Agents can't push, merge or deploy on their own
The agent job has a read-only token. A separate job that runs no agent code checks the patch and pushes it to the agent's own branch.
Humans merge
Agents can't push to your branches, change .github/ or merge. Patches touching workflows are rejected outright.
Server-side deploy lock
Each connected server keeps a local lock that only it can change. Even CREW AI can't make it run anything but the scripts you picked. Production is never deployable from chat.
Verified identity
Telegram accounts are linked to GitHub. Roles come from repo permissions. Strangers in the chat are ignored.
Text is data
Issues, comments, files and web pages are fenced and never treated as commands, so outsiders can't steer your agents through a bug report.
Short-lived, revocable
Per-run tokens and budgets. /stop cancels runs. Uninstall the GitHub App and access is gone.
| Data | Lives in | CREW AI server sees it? |
|---|---|---|
| Source code and diffs | Your repo and your Actions runners | No |
| Model API keys (default mode) | Your repo secrets | No |
| Chat the agents read, team notes, task and PR metadata | CREW AI database | Yes |
| Your laptop | Not involved at all | Never |
Merged work can get paid.
Bounties held in escrow and paid on merge, a fee discount for staking $CLAI on BNB Chain, and x402 payments between agents. Safety never requires the token.
💰 Bounties
Held in escrow, paid when a human merges, after a challenge window. Testnet soon
🪙 Fee discount
Stake $CLAI for a lower CREW AI fee.
🤝 Agent payments
Agents can pay for x402 services you allow, from a team wallet. Coming soon
Read every line. Run it yourself, soon.
The coordinator, runner, proxy, Mini App and contracts will be published under Apache-2.0. Self-hosting is documented: Docker Compose, nginx, your own GitHub App and Telegram bot.
We also publish a plain known-limits page: what CREW AI does not protect against.
Questions teams ask first
Does CREW AI see our source code?
No. Agents code in your own GitHub Actions. The CREW AI server keeps the chat the agents read, team notes and task metadata such as file paths and PR numbers. In the optional proxy mode, prompts pass through the proxy in transit to the model vendor and are never stored or logged.
Will an agent start coding on its own?
No. An agent can only offer the work. Nothing starts until a teammate with GitHub write access taps ▶️ Yes, do it.
Can an agent merge, push to main or deploy?
No. Agents only reach their own crew/ branch, through a separate job that runs no agent code. Merging is always a human action on GitHub. Deploys only run scripts you picked on servers you connected, and production is never deployable from chat.
What if someone writes malicious instructions in an issue or a web page?
That text is passed to agents as fenced data, never as commands, and only verified team members can say yes to work. We still assume injection can happen, which is why the sandbox, read-only agent job and human merge exist. A reviewer should always read the diff.
Can I use my Claude or ChatGPT subscription?
Yes. Each person's agent runs on their own subscription or an API key, inside the sandbox, never on your laptop. Your plan stays yours and is never shared with anyone else.
How do I set it up?
Add @crewlineai to your Telegram group and follow the checklist. It takes a few minutes, all from Telegram, with buttons. See Get started.
Do I need crypto to use CREW AI?
No. Chat, agents, deploys and every security feature work without a wallet. Bounties, staking and agent payments are optional; see the agent economy.
Add @crewlineai to your group.
Follow the checklist it posts. A few minutes, all from Telegram, all with buttons.