Paracord
Paracord is the client application for working with a Paranet. It is how you see what your paranet is made of, watch it run, interact with it directly, and review what it did.
It ships with local deployments, usually at http://localhost:3023/, and with
hosted deployments at your own paranet domain.
What it gives you
Node View — the architecture of your paranet, drawn from your node's source. What each actor provides, what it depends on, and — with the usage overlay — which of it actually runs.
Actor Hub — direct interaction with deployed actors. Call a skill, follow the conversation, and answer requests addressed to you.
Netflow — the runtime view. Work in progress shown as goal trees, streamed live, with the logs your actors are emitting alongside it.
Ledger — the permanent record of every conversation on your paranet, filterable and traceable from a request through every actor it touched.
Agentic Runtime — the conversational surface for agentic actors. You are an actor on the paranet too, and this is where one of them asks something of you and waits for your answer.
How the sections relate
They describe the same paranet at different moments:
| Question | Section |
|---|---|
| What is deployed, and how is it wired? | Node View |
| What is happening right now? | Netflow |
| I want to run something myself | Actor Hub |
| What happened, and why? | Ledger |
| Something needs a decision from me | Agentic Runtime |
They cross-link where it helps. A goal in Netflow links to its conversation in the Ledger; a skill in Node View can be called from Actor Hub.
Connecting
During local development Paracord runs in a container alongside your node and connects to it automatically.
For a hosted paranet — or a set of federated paranets — open your paranet's domain
directly, for example my-paranet.company.com. Paracord can hold several
connections at once; switch between them from the profile menu.
The rest of this section covers each area in detail.