Give a NanoClaw task room a persistent backend with shared rules
At a glance
ADHED's developer connected NanoClaw chat commands to a self-hosted task API whose rules apply to every client. This workflow is listed under task management, self-hosting, agent integration.
- Agents / tools
- NanoClaw, ADHED, Docker, life-cli.py
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Have Docker and a working NanoClaw installation. Clone dimatosj/adhed and run its `./setup.sh` to start the API. 2) Copy integrations/nanoclaw/life/ into NanoClaw's container/skills/life/. Put TASKSTORE_URL, TASKSTORE_API_KEY, TASKSTORE_USER_ID and TASKSTORE_TEAM_ID in NanoClaw's .env using the generated .adhed-credentials values; the URL must be reachable from the container. 3) Ensure container-runner passes those variables into the agent container. Run `npm run build` and `./container/build.sh` in NanoClaw, then restart its service. 4) Create a dedicated Tasks chat room. Ask the agent to add a task with a priority, list work in progress, and mark that task done. The agent uses life-cli.py to persist these operations. 5) Add server rules when needed, such as rejecting tasks without priorities, so all clients follow the same workflow.
Worth knowing
ADHED is API-only. Credentials in the host environment do not reach agents unless container-runner passes them through.
