Skip to content

Integrations: how it all fits together

Tramalia doesn't reimplement the ecosystem tools: it detects, wires and invokes them as separate programs. This section explains, tool by tool, what it is, how it's installed, what it requires and how it interacts with Tramalia and with the others.

What Tramalia requires (and what each tool requires)

Requirement Notes
Tramalia (core) Python 3.10+ only init, doctor, close, log, evidence, handoff run with nothing else
Pretty mode rich, questionary extra pip install ".[pretty]"
MCP façade mcp (SDK) extra pip install ".[mcp]"
Each external tool its own runtime binary, Python or Node — doctor tells you per project

Golden rule: the core governs with Python only. External tools are optional interop; if missing, Tramalia still governs and records it as a documented exception.

The integration model in 4 steps

flowchart LR
    classDef s fill:#eef1ff,stroke:#9a92e8,color:#2a2160;
    D["1 · tramalia detect<br/><small>what stack exists</small>"]:::s --> O["2 · tramalia doctor<br/><small>what's missing and how to install it</small>"]:::s
    O --> I["3 · mise install<br/><small>brings what's declared</small>"]:::s
    I --> C["4 · wiring<br/><small>mise.toml · .mcp.json</small>"]:::s
  1. detect identifies the stack → decides which gates/tools apply.
  2. doctor classifies each tool (bootstrap / stack / feature) and shows the exact install command.
  3. mise install brings everything declared in mise.toml (most of it).
  4. Tramalia wires them: commands in mise.toml (gates), servers in .mcp.json (Serena/Engram/…).

How each tool is installed (two ways)

Most are installed in two equivalent ways: directly (their official installer) or via mise (recommended — it's declared and auto-updates):

  • Via mise (recommended): mise use npm:repomix, mise use pipx:semgrep, etc. It stays in mise.toml and mise upgrade maintains it.
  • Direct: each tool's official installer (npm, pip, brew, binary…).

tramalia doctor always shows the recommended way for your project.

How they interact with each other (through Tramalia)

flowchart TB
    classDef core fill:#5b4bdb,stroke:#4335b0,color:#ffffff;
    classDef ext fill:#eef1ff,stroke:#9a92e8,color:#2a2160;

    AG["🤖 AI agent"]:::ext
    SR["Serena<br/><small>decides what to read</small>"]:::ext
    RP["Repomix / codebase-memory-mcp<br/><small>build the map</small>"]:::ext
    HR["Headroom<br/><small>compresses what was read</small>"]:::ext
    MI["mise<br/><small>runs the gates</small>"]:::ext
    EN["Engram<br/><small>remembers</small>"]:::ext
    T["🧩 TRAMALIA<br/><small>records what was done, what was validated, what evidence remains</small>"]:::core

    AG -->|navigates| SR
    SR -->|symbols| RP
    RP -->|context| HR
    HR -->|fewer tokens| AG
    AG -->|closes task| T
    T -->|mise run gates| MI
    MI -->|raw output| T
    T -->|opt-in export| EN

In words: Serena decides what to read, Repomix/codebase-memory-mcp build the map, Headroom compresses, mise runs the gates, Engram remembers — and Tramalia records what was done, what was validated and what evidence remains. Each actor does its part; Tramalia governs them.

The detail pages