# Codebase Integrations (`INTEGRATIONS.md`)

## Webhooks & APIs
- Currently, this project relies purely on Git synchronisation and CLI execution. Network activity is limited to downloading external packages (`npm install`, `pip install`, `git clone/pull`).
- Once MCP tools are invoked, `claude-mem` likely interacts with SQLite logic or LLM memory endpoints depending on its runtime schema. `browser-use` interfaces with web targets directly.

## Databases & Persistence
- There are no central RDBMS or NoSQL layers native to this orchestration layer.
- **Knowledge/Memory**: The project serves as an SSOT using markdown (`.planning/*`, `.agent/knowledge/*`).
- **MCP state persistence**: Relies on specific plugin's local DBs (e.g., SQLite for mem logs).

## Third-Party Authentication
- Configured by `.agent/config/.env.agent` which includes API keys (Vikunja Task ID, Gitea instances, etc.), though the current codebase only seeds and checks for its existence without directly invoking the APIs inside the shell scripts.

## Core External Tools
- **Git**: Primary persistence and vendor orchestration transport mechanism.
- **NPM & PIP**: Invoked asynchronously by bootstrap scripts to satisfy AI tool dependencies.
