Get started

From your Telegram group to a first pull request

Add the bot to your group and follow the checklist it posts. It takes a few minutes, all from Telegram. No server to run, and your code stays in your own GitHub.

What you need

A Telegram group

Where your team talks to the agents and approves their work.

A GitHub repo

Someone with admin or maintain rights on it does the GitHub steps. Teammates need write access.

An AI login

Your Claude Pro/Max or ChatGPT subscription, or an Anthropic or OpenAI API key.

Step 1: Add the bot to your group

Add @crewlineai to your Telegram group. The setup checklist appears right away. You can bring it back any time with /setup.

Anyone in the group can press its buttons. The checklist shows the whole team's progress, so it doesn't jump back when someone new taps it. Tap πŸ”„ Check again after each step.

Step 2: Connect GitHub and pick your repos

Tap πŸ”— Connect GitHub. GitHub opens, you choose the repos to install on, and your GitHub account is linked in the same visit.

Back in Telegram, the bot asks which repos this group works on. Tap βž• to add one. Only someone with admin or maintain rights on a repo can add it, and each repo belongs to one group. Change it later with /repos.

Step 3: Add the workflow file

Tap πŸ“„ Add workflow to …. GitHub opens with the file already filled in. Press Commit changes and don't edit it. The GitHub actions in it are pinned to exact commits and the AI tools to exact versions.

If GitHub asks you to accept new App permissions, the checklist shows an βœ… Accept new permissions button first. If it asks for two repo settings, open the settings page it links, set them, then tap βœ… Done. Most teams never see that step.

Step 4: Pick your AI and save its login

Choose a Claude subscription, Claude API key, ChatGPT subscription or OpenAI API key. The bot tells you what to copy: for Claude, run claude setup-token; for ChatGPT, run codex login and copy ~/.codex/auth.json.

Tap πŸ”‘ Connect your AI and paste it into the secure form. It goes straight to GitHub as an encrypted secret and never appears in the chat. Your agent then joins the group.

Step 5: Make the bot a group admin

Agents need to read the whole conversation. Open the group info, then Administrators β†’ Add Admin and pick the CREW AI bot. It needs no special rights.

Step 6: Just talk

Write what you need. Ask an agent directly with @its-name, or reply to its message. It answers live in the chat.

When something needs code, the agent offers it with ▢️ Yes, do it / βœ–οΈ No. A maintainer's Yes also approves the agent's plan, so it's one tap. A member's Yes still waits for a maintainer to tap βœ… Approve on the plan. The agent opens a pull request. A human always merges.

Chats are illustrations; the bot's exact wording may differ.

Teammates bring their own agent

Once setup is done, the checklist shows 🀝 Add your agent. New members also get it when they join the group. It opens a private chat with three steps: link GitHub, pick an AI, paste the login. A teammate needs write access to the repo on GitHub first. People without it can still chat, but agents never see their messages.

Where to click

The GitHub and Telegram steps people most often get wrong. The bot sends the same picture when you tap πŸ–Ό Show me where to click.

GitHub installation page: click Review request, then Accept new permissions.
Accept the App's permissions (only if the checklist asks). Review request β†’ Accept new permissions.
GitHub new file page: click Commit changes, keep Commit directly to main, click Commit changes.
Add the workflow file. Commit changes… β†’ directly to main β†’ Commit changes. Don't edit it.
Repo Settings, Actions, General: Allow all actions and Save, then tick Allow GitHub Actions to create and approve pull requests and Save.
Repo settings (only if the checklist asks). Allow all actions + Save, then tick β€œcreate and approve pull requests” + Save.
Telegram group info: Edit, Administrators, Add Admin, pick the CREW AI bot.
Make the bot an admin. Group info β†’ Edit β†’ Administrators β†’ Add Admin. No special rights needed.

Troubleshooting

β€œYou aren't an admin of any repo in that installation.”

Only someone with admin or maintain rights on a repo can connect it. Ask a repo admin to tap πŸ”— Connect GitHub, or to give you that role on GitHub.

β€œπŸ“¦ Installed. One more step: link your GitHub…”

The app was installed before your GitHub account was linked. Tap πŸ”— Link GitHub in that message. The install finishes by itself once you're linked.

β€œβ€¦ already belongs to another group.”

A repo works with one group at a time. Remove it in the other group first (/repos there, tap the βœ… repo).

β€œThis link is invalid or expired. Start again from Telegram.”

Setup links work once and expire after 30 minutes. Tap πŸ”„ Check again in the checklist for a fresh one.

β€œπŸ”‘ … has no AI login yet.”

The agent's owner still has to save a login. Open /setup and tap πŸ”‘ Connect your AI. If the form says β€œThat doesn't look like a Claude login token”, run claude setup-token again and copy the line that starts with sk-ant-oat.

β€œπŸ”‘ … is added. Agents need their login saved there too”

Logins are saved per repo. When you add a repo later, each agent's owner taps πŸ”‘ Save my AI login again and pastes it once more.

β€œβŒ Couldn't start … Is the CREW AI workflow file in the repo?”

The file .github/workflows/crewline.yml is missing from the default branch. Use the πŸ“„ Add workflow button in /setup.

β€œβŒ The agent's run failed before it could answer.”

CREW AI noticed the GitHub run ended without reporting back. Tap Open the run in that message to see why. The usual causes are a missing or expired AI login, or a workflow setting.

β€œβŒ› No answer came back.”

GitHub never started the run, or it stopped without a word. Check the repo's Actions tab, then ask again. Runs that haven't started after 5 minutes are closed with this message.

β€œβ³ … is still answering the previous message.”

Each agent answers one message at a time. Wait a minute and ask again.

β€œπŸ›‘ This chat hit today's limit of agent answers.”

Each group has a daily limit of agent answers. It resets 24 hours later.

β€œOnly maintainers can approve plans.”

Plans need someone with admin or maintain rights on the repo. Roles come from GitHub and are refreshed every 10 minutes.

The agents ignore my messages

Agents only read people who linked GitHub and have write access to the repo. If the checklist says β€œMake me a group admin so I can read the chat”, make the bot an admin (see the picture above).

β€œLink your GitHub first: DM me /link”

Open a private chat with the bot and send /link. Linking only happens in a private chat, so nobody else can use your code.

I'd rather host it myself

You can. Follow the self-hosted setup; the source will be published under Apache-2.0.

Ready when your group is.

A few minutes, all from Telegram.