Jigsaw
Fregoli is one piece of a growing family of projects, big and small. Here is how the pieces fit together, as seen from this one.
Fregoli you are here
A web application an agent can rewrite while it is running: capabilities are Cordis plugins mounted and unmounted in a live Node process.
Hermetarium habitat
The world an agent wakes up in: an OCI image it may use freely as root, behind a wall with Squid as the only, logged way out.
The house Fregoli may move into. Fregoli's docs recommend running it as a Hermetarium inhabitant (its own image serving port 8080 behind a runc or Firecracker wall, with Squid as the only, logged road out and model keys kept in the host ACL), yet never require it: a plain laptop node process is a valid home too. Fregoli's image is ready for the move: it listens on all interfaces and carries ip and iptables. Running it inside a habitat end to end has not been tried yet; that is open work on Hermetarium's side (hermetarium#10).
grok-budget-mcp possible budget gauge
A small local MCP server that tells a Grok Build agent how much of its weekly usage pool is left, the same figure as /usage. Read-only, unofficial endpoint.
A small gauge Fregoli could use to keep an eye on cost. Fregoli’s agent is the Grok CLI, started over ACP, and Grok can load extra MCP servers from .grok/config.toml; with this one loaded, the agent could ask how much of the weekly pool is left, stop when the budget runs out, or warn the user first. Nothing of this is wired up yet: today Fregoli hands Grok only its own MCP server.
claude-budget-mcp possible budget gauge
A small local MCP server that tells a Claude Code agent how much of its 5-hour and weekly usage limits is left, the same figures as /usage. Read-only, unofficial endpoint.
The Claude Code counterpart of the budget gauge. Fregoli could use it the same way: ask how much of the 5-hour and weekly limits is left, stop when they are used up, or warn the user. It would need a Claude Code agent, and today Fregoli starts the Grok CLI as its agent, so this use is further off than its sister’s and not built yet.
Git Warden kin
Guard posts between AI agents and their Git remote: a Push Guard that checks every push with deterministic rules, and a Backup Guard that keeps an append-only backup of every branch and tag.
A fellow piece of the same puzzle; no direct connection yet.