Renoa

Renoa is a modular agent system built around one small, non-replaceable durable kernel. The kernel preserves execution truth: stable identities, command admission, ordered state, effects, cancellation, recovery, semantic history, and frozen runtime revisions.

Everything that defines an agent's behavior stays replaceable outside that kernel: model provider, agent loop, context and compaction strategy, tools, skills, workspace policy, permissions, and surfaces.

surface -> Renoa Host -> Renoa Kernel -> resolved loop and effect adapters
                |
                `-> profile + model + context + tools + workspace policy

The local Host assembles a concrete Agent instance from those pieces for each new operation. The kernel freezes that exact assembly, then executes it durably. This is the base for adding different agents and future capabilities without turning the kernel into product policy or one giant plugin interface.

Current local coding path

• renoa-kernel is the non-replaceable durability core.
• renoa-agent defines provider-neutral messages, models, tools, and streaming events.
• renoa-agent-loop is the replaceable model/tool loop with durable, replaceable context compaction.
• renoa-local is the first Host. It composes Renoa Alpha, the Renoa-owned model-provider adapter, the compaction strategy, and six local coding tools.
• renoa-acp is a thin ACP v1 surface adapter. A compatible frontend launches renoa-agent acp; ACP translates UI messages and live updates but does not own agent composition or durability.
• renoa-telegram is the first hosted surface. It maps private Telegram topics to durable sessions of Arcee, Renoa's personal-operator profile, while leaving composition and history with the Host and kernel.
• control-room is the first browser RCP surface. It uses passkeys, shows the Host's real task directory and durable event replay, follows live execution, and submits idempotent continuation commands. Its IndexedDB cursor and outbox remain surface state; the one-use connection ticket remains memory-only.
• renoa-registry is the optional private service that makes immutable Agent Plugin packages available to more than one Host. Its wire contract lives in renoa-registry-protocol. It carries no credentials, profile permissions, sessions, or RCP events.
• mcp-client-node is the replaceable MCP process adapter. The Host durably registers connections, publishes complete catalogs, owns optional browser OAuth and refresh, and exposes only deferred search/load/execute schemas to Alpha.
• mcp-registry-node is the replaceable, read-only downstream adapter for official MCP Registry discovery. plugin_search can search names and inspect one exact published version, but Registry metadata never becomes an installation input. Alpha must still verify the provider's official documentation before adding the normalized MCP definition. Exact local Agent Plugin packages use the same Host manager.

Alpha currently has read_file, edit_file, write_file, bash, grep, and find. Model and reasoning choices can change between operations. Workspace AGENTS.md instructions are read again for every new operation, while an already admitted operation keeps its frozen behavior.

Agent chat surfaces can connect through ACP without entering the kernel. After configuring a provider as documented in renoa-local, build and start the surface-neutral ACP process with:

cargo build -p renoa-acp
./target/debug/renoa-agent acp

RCP is separate

RCP is Renoa's continuity layer for authenticated communication and handoff across surfaces and execution nodes. It remains separate from the Agent path and does not replace, wrap, or define the kernel.

The Rust coordinator still listens only on loopback. The first public proof reaches it through TLS at wss://renoa.live/connect. A real Alpha tool turn and two-surface continuation crossed that origin without sharing credentials or cursor state; deterministic tests cover the same durability boundaries. This is a candidate deployment, not a stable public wire release. The browser Control Room and the Discord surface now use that RCP boundary; Waku and Telegram are not yet connected through it. Canonical continuity decisions live in docs/rcp-v0.md.

License

Renoa is available under either the Apache License, Version 2.0 or the MIT license, at your option.

Unless explicitly stated otherwise, contributions intentionally submitted for inclusion in Renoa are provided under those same terms without additional conditions.

Start with the current renoa-kernel contract, Host architecture, extension-system north star, direct MCP contract, Alpha profile, agent-loop contract, and ACP adapter.

For continuity work, docs/rcp-v0.md remains canonical. docs/harness-v0.md and docs/kernel-v0.md are archived records of superseded implementations, not the current Renoa architecture.