# TeammateX 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. - Findings24: - Site: - Preços: Freemium - Categorias: Base de Conhecimento IA, Grafo Conhecimento IA, Assistente de Código IA ## O que é TeammateX? 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. ## O que TeammateX pode fazer? ### Repository onboarding pipeline 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. ### Evidence-backed code answers 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. ### Ownership and dependency mapping 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. ### Pull-request workflow 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. ### Team workspace and operations 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. ### Self-hosted controls and observability 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. ## Casos de uso ### Onboard engineers to an unfamiliar codebase 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. ### Find the right owner or reviewer 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. ### Assess change impact 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. ### Investigate bugs and stack traces 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. ### Automate small maintenance fixes 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. ## Perguntas frequentes ### How is TeammateX deployed? 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. ### Which repositories can it learn from? 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. ### Does code leave the user's infrastructure? 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. ### Can TeammateX make code changes? 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. ### Which language models are supported? 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. ## Informações rápidas - **Product type**: Self-hosted AI teammate for software teams - **Repository source**: GitHub - **Deployment**: Docker Compose - **Knowledge systems**: pgvector embeddings and Neo4j knowledge graph - **Status**: Beta; MIT license - **Pricing**: Not established in the supplied product sources