TeammateX is a self-hosted AI teammate for software teams. It learns repositories from GitHub, builds searchable code and ownership knowledge, answers with file-and-line evidence, and can create pull requests.
TeammateX is a self-hosted AI teammate for software teams. It connects to GitHub, imports repositories, parses their source code, mines Git history, and builds a combined knowledge base of code meaning, code structure, and ownership.
The product uses semantic search and embeddings for questions about what code means, while a Neo4j knowledge graph represents relationships such as CALLS, OWNS, and PART_OF. This lets the agent answer repository questions with file-and-line receipts, inspect dependencies and blast radius, and identify likely owners from commit history.
Beyond question answering, TeammateX can operate on a repository: it edits files, runs tests and lint, creates branches and commits, and opens pull requests. Its self-hosted Docker Compose deployment keeps repositories, embeddings, and graph data on the user's infrastructure, with support for provider-hosted LLMs or a local Ollama model.
Connect GitHub repositories individually or bulk-select repositories, then track cloning, tree-sitter parsing, embedding, graph construction, and Git-history mining as separate stages. Failed stages can be retried, and a background poller re-syncs knowledge every 15 minutes.
The agent combines semantic search, graph queries, blame, commit logs, and repository files to answer technical questions. Responses can include file-and-line receipts rather than relying only on generated text.
Git history is used to associate contributors with code, while graph relationships expose call edges, dependents, dependencies, and architecture. This supports owner lookup and impact analysis before a change is made.
The agent can read and edit files, create a branch, run tests and lint, commit changes, and open a real pull request through its Git tooling.
The application includes streaming chat with thread history, a task kanban, standup and weekly-digest views, team ownership records, knowledge cards, audit history, cost tracking, and live container logs.
Docker Compose runs the stack on the user's infrastructure. LLM calls are metered with a monthly budget guardrail, agent actions are audited, logs are available in the UI, and API access requires login with admin-only account creation.
A new contributor can ask how a subsystem works, search for relevant implementation details, and inspect the concepts and relationships TeammateX learned from the repositories instead of starting with manual codebase exploration.
When a change needs review or an incident needs an informed responder, the team can query ownership mined from Git history and inspect the relevant repository context.
Before modifying a function or subsystem, developers can query callers, dependents, and dependencies to understand potential blast radius and investigate how a change connects to the rest of the system.
A developer can attach a stack trace and combine it with semantic code search, graph lookups, blame, and commit history to trace an issue through the repository and identify relevant code or owners.
For bounded changes, the agent can modify files, run tests and lint, commit the result on a branch, and open a pull request for human review.
It runs on the user's infrastructure through Docker Compose. The published quickstart lists Docker, Compose v2, approximately 6 GB of free RAM, and an LLM key or a local Ollama model as requirements.
The supplied site describes GitHub-based onboarding. Repositories can be added individually or selected in bulk from the repositories associated with the connected GitHub account.
The product is designed to keep code, embeddings, and graph data on the user's servers. With local embeddings and a local Ollama model, the site states that nothing leaves the box; using hosted LLM providers sends model requests to the selected provider.
Yes. Its documented workflow can edit files, create a branch, run tests and lint, commit files, and open a pull request. The resulting change is represented as a real PR rather than only a suggested code snippet.
The site lists DeepSeek, OpenAI, Anthropic, Groq, and Ollama through LiteLLM. Ollama can be used for a local model, and local embeddings are the default.
autonomyai.io
AutonomyAI is an AI-native product delivery platform that helps product managers and designers turn ideas into production-ready code changes in their existing codebase. Engineers review and approve the resulting pull requests before merge.
hacktron.ai
Revisão de código e segurança de aplicações com IA para encontrar vulnerabilidades exploráveis em pull requests
cubic.dev
cubic é uma plataforma de revisão de código com AI para bases de código complexas. Ela ajuda as equipes a detectar bugs em pull requests e verificar repositórios em busca de problemas antes do merge ou lançamento.
oomol.com
OOMOL conecta Gmail, GitHub e Notion a agentes de IA para reutilizar ferramentas autorizadas no Codex, Claude Code e Cursor, com planos gratuitos, pagos e por consumo.
verdent.ai
Verdent AI é uma suíte de programação agêntica que transforma objetivos de software em linguagem natural em tarefas, builds e resultados de testes para VS Code, desktop, Mac, Windows, Slack e Telegram.
haystackeditor.com
Haystack é uma ferramenta de revisão de código com tecnologia de IA para fluxos de trabalho de pull requests. Ajuda as equipes a classificar PRs, identificar alterações arriscadas e direcionar revisões com base em decisões registradas, responsáveis e contexto.
