Directories
¶
| Path | Synopsis |
|---|---|
|
Package all registers every built-in plugin.
|
Package all registers every built-in plugin. |
|
Package budget holds each gateway key to the limits its owner set (#585): the tokens or estimated cost it may use in a window.
|
Package budget holds each gateway key to the limits its owner set (#585): the tokens or estimated cost it may use in a window. |
|
Package gateway is the Gateway page: the gateway's state, its keys, how to connect a client, the models it serves and its recent calls.
|
Package gateway is the Gateway page: the gateway's state, its keys, how to connect a client, the models it serves and its recent calls. |
|
Package groups is routing groups: several models agents pick as one, each request sent to the right one and on to the next when one fails.
|
Package groups is routing groups: several models agents pick as one, each request sent to the right one and on to the next when one fails. |
|
Package library is the Library page: instructions, MCP servers, skills and hooks, kept once and given to every agent.
|
Package library is the Library page: instructions, MCP servers, skills and hooks, kept once and given to every agent. |
|
Package middleware is the JS gateway plugins: the plugins with a gateway module in plugins.json, run in the gateway's own process (docs/subsystems/gateway-middleware.md).
|
Package middleware is the JS gateway plugins: the plugins with a gateway module in plugins.json, run in the gateway's own process (docs/subsystems/gateway-middleware.md). |
|
Package otel is Settings' Observability: each request's traces and metrics sent to an OpenTelemetry collector, such as Langfuse.
|
Package otel is Settings' Observability: each request's traces and metrics sent to an OpenTelemetry collector, such as Langfuse. |
|
Package redact is Settings → Privacy's masking: secrets, personal data and the user's own words go to a vendor as placeholders, and come back as they were.
|
Package redact is Settings → Privacy's masking: secrets, personal data and the user's own words go to a vendor as placeholders, and come back as they were. |
|
Package rotation is the routings a provider or group can be set to besides Smart: In order, In turn, Least used first, Weekly pace and By weight.
|
Package rotation is the routings a provider or group can be set to besides Smart: In order, In turn, Least used first, Weekly pace and By weight. |
|
Package routing is the Routing page: each request the gateway routes, played as it decides, the accounts it weighed and what each answered, and the routing groups' editor.
|
Package routing is the Routing page: each request the gateway routes, played as it decides, the accounts it weighed and what each answered, and the routing groups' editor. |
|
Package search is magpie's web search for a model that can't search by itself: the agent's web_search tool, answered by a provider that can search or a search API set up in Settings.
|
Package search is magpie's web search for a model that can't search by itself: the agent's web_search tool, answered by a provider that can search or a search API set up in Settings. |
|
Package sessions is the Sessions page: the agents' past conversations, to read, search, resume and export.
|
Package sessions is the Sessions page: the agents' past conversations, to read, search, resume and export. |
|
Package tools serves the tools the user's plugins give (their OpenCode tool hook) to every agent, over magpie's plugin tools MCP server (internal/gateway/tools_mcp.go, docs/subsystems/plugin-tools.md).
|
Package tools serves the tools the user's plugins give (their OpenCode tool hook) to every agent, over magpie's plugin tools MCP server (internal/gateway/tools_mcp.go, docs/subsystems/plugin-tools.md). |
|
Package usage is the Usage page: the allowances, what was spent and on what, the sessions, each request, and what filled the context window.
|
Package usage is the Usage page: the allowances, what was spent and on what, the sessions, each request, and what filled the context window. |
|
Package warmups is warm-up and check-in: start a subscription's usage window at a time the user picks, and claim vendors' daily check-in credits.
|
Package warmups is warm-up and check-in: start a subscription's usage window at a time the user picks, and claim vendors' daily check-in credits. |
Click to show internal directories.
Click to hide internal directories.