Meltemi
Four integration levels, stated honestly
Not every agent can be piloted the same way, so Meltemi declares the level each one reaches instead of pretending they are equivalent. The fleet view shows the level, whether the binary was detected, and what to install when it was not.
| Level | What it means | What you get |
|---|---|---|
| 1 | Speaks the agent-client protocol natively | Full piloting: streamed turns, permission prompts, resume. |
| 2 | Reached through a protocol adapter | The same piloting, once both layers are present: the agent's own command-line tool and the adapter that bridges it. |
| 3 | Headless run with structured output | One-shot turns whose structured output is mapped into the session log — including usage counters when the output reports them. |
| 4 | Context projection only | No process is piloted: Meltemi writes the context file the tool reads, and the tool stays in your hands. |
A level-2 agent needs two things installed, which is the most common reason detection looks wrong. The fleet view names the missing layer and prints the exact command that installs it.
Several subscriptions at once
Launch profiles let you run more than one account of the same provider — work and personal, or two seats of the same plan — by redirecting the authentication context the official binary reads. Meltemi never reads, stores or forwards credentials: it passes the context you named and the binary authenticates itself.
Each session records which agent and which subscription ran it, so a project can hold several sessions across several accounts and you can still tell them apart — in the project tree, in the session list and in the usage accounting.
Fair play, by rule
Official binaries only
Meltemi executes what the vendor published, with the vendor's own authentication. It never impersonates another client's traffic or identity.
No credentials, ever
Reading, storing or reusing an agent's credentials is forbidden by the constitution, not by convention. Profiles carry a context name, never a secret.
Nothing bundled
No third-party agent is packaged or redistributed. Where an integration path is tolerated rather than sanctioned by its vendor, the fleet view says so in plain words.
Getting your first agent running
Install Meltemi, ask it what it can see, and let it tell you what is missing. The fleet view is the answer to “why is my agent not detected”, and it carries the remedy with it.