____ _                 _        _____                                    _       
  / ___| | __ _ _   _  __| | ___  |_   _|__  __ _ _ __ ___  _ __ ___   __ _| |_ ___ 
 | |   | |/ _` | | | |/ _` |/ _ \   | |/ _ \/ _` | '_ ` _ \| '_ ` _ \ / _` | __/ _ \
 | |___| | (_| | |_| | (_| |  __/   | |  __/ (_| | | | | | | | | | | | (_| | ||  __/
  \____|_|\__,_|\__,_|\__,_|\___|   |_|\___|\__,_|_| |_| |_|_| |_| |_|\__,_|\__\___|

Claude Teammate is an AI bot that works around the clock - picking up tickets, writing plans, opening PRs, acting on feedback, and reviewing code. No stand-ups. No Slack pings. No passive-aggressive "per my last email." Just like your best teammate, minus the coffee breath.

Assign it tickets. It ships.

| | Step | What happens | | ------ | ------------------ | ----------------------------------------------------------------------------------------------------- | | 01 | Assign the ticket | Assign the Jira ticket to the bot. | | 02 | It plans | Reads the codebase and writes a plan. You give feedback, it revises. Nothing moves until you approve. | | 03 | It ships | Opens a PR. Responds to feedback. Keeps going until it's merged. | | 04 | It remembers | Retains build commands, known pitfalls, and lessons from every task it has shipped - so the next ticket in the same epic starts smarter. |

Claude Teammate is right for you if

• ✅ You want Jira tickets to turn into merged PRs without manual handoff
• ✅ You want PR review comments acted on, not just acknowledged
• ✅ You need a reviewer that always shows up and leaves structured feedback
• ✅ You want automated PR review without adding another review subscription on top of Claude
• ✅ You want an AI that remembers - which repo, what's shipped, what breaks, what to avoid
• ✅ You want the agent running in its own working environment so it can test code and verify real outputs
• ✅ You want this running on your own infrastructure

How It Works

Review Human PRs Too

Claude Teammate is not limited to tickets it implemented itself. Add it as a reviewer on a human-authored pull request and it will read the diff, inspect the repository, and leave structured review feedback. This can be an alternative to paid tools like CodeRabbit or GitHub Copilot code review.

It Remembers

Every epic has its own memory. The bot picks up exactly where it left off - no matter how much time has passed.

That memory is built from more than the original Jira description. Claude Teammate updates it from planning, implementation, review comments, and recurring human feedback so future tickets inherit the durable parts of the work instead of starting from scratch.

memory/
└── {domain}/
    └── {workspace}/
        └── epic-{jira-key}.md

| Field | What it stores | |---|---| | jira_key / jira_url | Canonical epic identity | | repos | Shared target GitHub repositories for the epic | | facts / guardrails | Reusable lessons, build quirks, verification workflows, recurring human feedback, and what-not-to-do notes for the epic |

The memory stays compact on purpose. It is cleaned up, deduplicated, and summarized over time so later tickets can reuse the important context without dragging an ever-growing prompt window behind them.

Quickstart

Requirements:

• Node.js 20+
• Claude CLI installed and authenticated
• A Jira API token
• A GitHub PAT with repo + PR permissions

Installation

npm install -g claude-teammate

Run tm8 as a dedicated non-root OS user. On a VM, create that user and hand ownership of the workspace and runtime directories to it before starting the worker.

Example VM setup for a dedicated service user:

sudo npm install -g claude-teammate
sudo useradd --create-home --shell /bin/bash tm8
sudo mkdir -p /home/tm8/.tm8
sudo chown -R tm8:tm8 /home/tm8/.tm8
sudo chmod -R u+rwX /home/tm8/.tm8
sudo chmod -R a+rX "$(npm prefix -g)/lib/node_modules/claude-teammate"
sudo su - tm8
claude login
tm8 start

If you run tm8 start --local, also hand ownership of that project directory to the same user before starting the worker.

start creates ~/.tm8/.env on the first run. If that config already exists with the required values, setup is skipped and your credentials are not prompted for again.

# .env file generated by `tm8 start`
JIRA_BASE_URL=https://yourorg.atlassian.net
[email protected]
JIRA_BOT_API_TOKEN=...
GITHUB_PAT=ghp_...

To run multiple agents on the same machine, use --local to store agent status and memory in the current working directory.

To upgrade to latest version

npm install -g claude-teammate@latest

Check or stop the worker with:

sudo su - tm8
tm8 status
tm8 stop

Runtime files and memory are stored in:

~/.tm8/
├── .env
├── .claude-teammate/
    ├── repos/
    ├── worker.log
    ├── worker.pid
    └── state.json
└── memory/
    └── {domain}/
        └── {workspace}/
            ├── epic-{jira-key}.md
            └── issue-{jira-key}.md

FAQ

How is this different from just prompting Claude directly? Claude Teammate is a persistent, scheduled process. It doesn't wait for you to type - it polls, acts, and remembers.

What happens if a Jira issue lacks context? It asks. The bot comments on the Jira issue with clarifying questions and waits for answers before doing anything.

Can it handle multiple Jira workspaces and GitHub repos? Yes. Each epic is scoped to its own Jira domain and workspace, and can map to one or more GitHub repositories.

Does it understand the codebase or just generate generic code? It reads the actual repository before writing anything - structure, conventions, existing patterns. The plan it proposes is specific to your code, not a template.

Can it test code and verify UI changes? Yes. It works in its own cloned working environment, can run the repo's test and build commands, and can use Playwright to take screenshots and verify frontend changes instead of relying only on the diff.

Can I use Claude skills or MCP, and does it respect CLAUDE.md? Yes. Claude skills, configured MCP servers, and repo instructions in CLAUDE.md are available and respected just like they are in a normal Claude-driven workflow. Playwright MCP is built in and enabled by default so challenging frontend tasks can be verified in-browser.

Roadmap

• Act on per-line PR review comments
• Ensure no conflicts for multiple concurrent claude-teammate agents
• GitLab support
• Bitbucket support
• Slack and Teams integration

Contributing

Contributions are welcome. Open an issue to discuss before submitting large changes.

Community

• GitHub Issues - bugs and feature requests
• GitHub Discussions - ideas and questions

Disclaimer

This software is provided "as is", without warranty of any kind. The authors and contributors are not responsible for any damage, data loss, or unintended consequences arising from the use or misuse of this project. Use at your own risk.

License

MIT © 2026 Claude Teammate