Menu
Describes the current local development setup, for when we want to perform development tasks on the actual Rhizome app
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
How to talk to the deployed plurama apps (treina, …) from the shell with the plurama-cli command — a curl-like client that carries baked-in prod credentials. Use whenever a task means reading or writing live plurama app data over HTTP, when `plurama-cli` is missing or unauthorized, or when a new app must be added to it.
Tracker's HTTP API — authenticate as a machine user, read tasks/meets/journals/today-board, ingest mail messages, write through the recording-mode gate via curl
How to run, test and develop the natural-language Telegram bot that queries tracker. The bot is NOT in tracker — it lives in the plurama umbrella app (plurama/src/plurama/app/agent). Covers the agent architecture, the secrets/config it needs, the locked-box egress-proxy gotcha, seeding a testable conversation, and driving it from the host as if you were Telegram.
To develop the user interface of the application, you need to know how to start, stop, restart the app and where to find it.
Rhizome's local REST API — search, read, and create contexts/items via curl
Sandbox a Docker container so only an explicit allowlist of outside hosts is reachable. Use when running an untrusted/AI agent container and you want a hard egress cutoff with optional inbound port forwarding.
| name | rhizome-development |
| description | Describes the current local development setup, for when we want to perform development tasks on the actual Rhizome app |
The preferred setup is a CMUX workspace (expect us to not work on more than one feature simultanously on a single machine,
so we also confine ourselves to a single workspace and you can expect us to not need to reach outside our single cmux workspace), where we, in the left pane of two panes, coordinate from a claude session (the coordinator), in the upper pane of a vertical split, in its terminal surface, another agent, which sits in the lower pane in its
vertical split, in its own terminal surface.
That agent is the doer. We want the doing be happening in a sandbox.
Normally in one where the internet is cut off (make yolo), and when the feature(s) we are working on demand,
one which has vector db support. For reference, see rhizome/README.md.
Interaction happens between the human and the coordinator, and then, autonomously, between the coordinator and the doer.
I want full visibility, that's why I want handoffs to happen in the cmux surfaces (use cmux CLI).
We commit directly to the main branch, and want specifically most, if not all, commits, come from the in the box agent, as it has its own git handle which we can easily recognise.
