passioncode-ai/fabric-agent-adapter

**Fabric Agent Adapter** makes any agent Fabric-compatible. Fabric is PassionCode.ai's
product, the CEO AI agent: you talk to Fabric, and it chooses, binds and runs the agents that
do the work. This adapter is how an agent becomes one Fabric can bind — four Agent Skills,
Python and Node reference kits and a live conformance probe for the
Fabric Agent Contract. It also works
on its own: the skills, kits and probe need no Fabric install.
The skills are adapting-projects-to-fabric, creating-fabric-agents,
building-fabric-services and working-with-fabric.
working-with-fabric is for the other side: a coding agent (Claude Code, Codex, Kimi Code, Kilo, Hermes) opened in
a terminal that works in a project through Fabric. It finds Fabric (hub.json, its pid), has the machine's
lifecycle broker start it when it is down, registers fabric-mcp once with no secret, calls fabric_whoami
first, reads the project board (com.status, com.list, com.read_ack only what was read) and asks other
Projects only through com.submit, asks who is working on what and claims its task before it starts
(fabric_work_list, fabric_work_claim, Fabric 0.4.0), links tasks to backlog rows instead of copying them, and
releases at the end (fabric_work_release). scripts/fabric_session.py status prints where Fabric stands and one
next action:
In Claude Code the plugin adds four session hooks: SessionStart puts that preamble into the session when the MCP
server fabric is registered (one line pointing at the broker when Fabric is down), with the machine's
Fabric-service count; Stop records each turn's facts (HEAD, files changed, lines added and removed — never content)
and the board's unread count; UserPromptSubmit adds one line only when that count rose; SessionEnd releases what the
session left claimed. Stop, UserPromptSubmit and SessionEnd act only when the running Fabric advertises
session-hooks/1. All are silent in a session Fabric launched, never block the session, read no token and always
exit 0. fabric_session.py watch-mail waits for board mail under a background watcher, and install-host-hooks
--host codex|kimi adds the session-start preamble to Codex or Kimi Code (a dry run unless --apply). The
hooks reference lists what
they need from Fabric; the board reference
is the board-first workflow.
building-fabric-services makes an agent a long-lived local service with a dashboard
that is always alive, runs as one copy, keeps its state through a reinstall and appears
in Fabric Dashboards by itself — the fabric-service/0.1 extension. It also makes an **online** agent
or dashboard — an https origin on a platform — a Fabric service (the remote placement, DEC-0019): the same
four routes behind the token, a __Host- session cookie, and one descriptor on the operator's computer;
scripts/sample-remote-service.mjs is the complete example. It ships Python and
Node reference kits (scripts/fabric_service.py, scripts/fabric-service.mjs), a
complete scripts/sample_service.py, and scripts/check_service.py, a live probe. A service that answers
requests other Projects post to its Project on Fabric's project board uses the board responder
(scripts/fabric_hub.py and scripts/fabric_board.py, Node fabric-hub.mjs and fabric-board.mjs): the
board.respond grant, enroll, claim, accept the exact digest, complete, a checkpoint before every step, and restarts
that reconcile or take accepted work back by a transfer (the board reference):
The dashboard itself is built from the **dashboard kit** (assets/dashboard-kit/, fabric-dashboard/0.1,
contract DEC-0036): one stylesheet and one script that keep the page usable from 360 CSS px inside a host
pane beside the agent console — navigation that folds into a More menu, wide tables in their own scroll
box, sticky chrome at most 120 px — with seven WCAG AA themes (light and dark) that follow the host's