CtrlK
BlogDocsLog inGet started
Tessl Logo

jbaruch/nanoclaw-trusted

Rules for trusted NanoClaw groups. Shared memory, session bootstrap, cross-group memory updates. Loaded for trusted and main containers only.

74

Quality

93%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

Overview
Quality
Evals
Security
Files

async-tasks-extended.mdrules/

alwaysApply:
Yes

Async Tasks — Extended Protocol

Trusted-tier extension of the core async-tasks protocol (jbaruch/nanoclaw-core: telegram-protocol).

Runtime message protocol

  1. Note the <message id="..."> for reply threading.
  2. Optionally upgrade the reaction once you've inspected the request — a follow-up mcp__nanoclaw__react_to_message call supersedes the runtime emoji.
  3. Spawn Agent with run_in_background: true. Tell it to send results via mcp__nanoclaw__send_message with reply_to set to the original message ID.

Scheduled tasks

Scheduled tasks (heartbeat, morning brief, reminders) have no user message to acknowledge. No ACK; silent results send nothing.

Post-compaction

Do NOT resume an async task inline. Restart with a fresh background agent.

CHANGELOG.md

README.md

requirements-dev.txt

tile.json