@faiber/faiber-manage

Typed browser and server client for the project-scoped Faiber Manage gateway, including service proxy origins and the Manage Agent interaction protocol.

npm install @faiber/faiber-manage

import {
  FaiberClient,
  ManageApi,
  domainsFromManageProxy,
  isManageAgentActionEvent,
  parseManageAgentEvents,
} from "@faiber/faiber-manage";

const domains = domainsFromManageProxy(window.location.origin);
const manage = new ManageApi(new FaiberClient("manage", {
  domains,
  authMode: "cookie",
}));

const me = await manage.me();
const models = await manage.listAgentModels();
const thread = await manage.createAgentThread({ title: "Manage products" });
const stream = await manage.openAgentChatStream(thread.data.id, {
  message: "Show products with low inventory",
  agent_slug: "manage",
  project_slug: me.data.project.slug,
});

for await (const event of parseManageAgentEvents(stream.data)) {
  if (isManageAgentActionEvent(event)) {
    // Render and confirm mutations before calling executeServiceAction.
    console.log(event.data.arguments);
  }
}

listAgentModels returns the Agentic model catalog used by helper settings and chat composition. Durable chat management is available through listAgentThreads, getAgentMessages, cancelAgentChat, and deleteAgentThread.

domainsFromManageProxy configures normal Faiber service clients through Manage's project-scoped /api/v1/proxy/{service} boundary. Prefer those typed service clients for known operations. executeServiceAction exists for runtime actions proposed by the Manage Agent, and callers must review destructive or privileged actions before execution.

All methods return complete Axios responses. Request options accept headers, timeouts, AbortSignal, credentials, adapters, and interceptors through the shared client. Cookie mode is recommended because Manage sessions are HttpOnly and project scoped. Stream requests default to Axios's fetch adapter so browser ReadableStream responses remain incremental; consumers may supply another streaming adapter.

Axios errors retain HTTP status, response headers, request IDs, and backend details. Agent event parsing is transport-only: it never auto-executes an action. The complete facade is available from @faiber/faiber-ts-sdk.