vhaudiquet
12ba97c8f1
The Dockerfiles copied every framework crate's manifest because the old root workspace path-patched crossterm and carried in-tree resolution. The claw resolves from crates.io now, so the builder copies only the claw's own manifests, and the vendored-crossterm COPY (and its explanation) is gone.
ῥῆμα, "the spoken word": words that do things.
Rhema Claw
Rhema Claw is the resident tier of the Rhema agent framework: a claw-shaped daemon that watches forges (GitHub, Gitea, GitLab) and calendar feeds, dispatches work to its agents, and serves a chat surface over HTTP — native routes plus an OpenAI-compatible shim, with a web UI and an Android client talking to it.
The framework it embeds (the crates under crates/ it pulls from
crates.io: rhema-autonomous-agent, rhema-coding-agent,
rhema-rsd, and friends) lives in the
rhema repository.
Layout
crates/rhema-claw/— the daemon: forge watches, session dispatch, the chat surface, MCP wiring, and the vision helper. See its README.integrations/— the feed adapters that normalize forge and calendar activity intorhema-rsddispatch.tools/— what runs on the user's machine: therhema-claw-tools-contract(the scoped agent-token allowlist the auth middleware enforces), the shared thin-client code, andrhema-claw-tools-notify.web/claw/— the Nuxt web UI.android/— the Compose Android client.deploy/— the Docker images and the Helm chart.