Example: remote ack bot, a hosted agent type with a localhost provider

[baxen]

Stacked on #870. Kept as a draft for reference; not for merging.

examples/plugins/remote-ackbot is a hosted Agents type plus a Node provider on 127.0.0.1:8787. The provider holds each agent's key, takes the owner's NIP-OA attestation, publishes the agent's profile and answers its owner's mentions with "ack". It reads and writes the community over HTTP with NIP-98 and the attestation as x-auth-tag, as the app's own agents do.

Its replies carry the app's ms tag, set at least a millisecond after the message they answer. Without it, a reply in the same second as the mention could sort above it.

Trying it

1. node examples/plugins/remote-ackbot/server.mjs. Add FAIL_ACTIVATE=1 to try Finish setup.
2. bin/just desktop. It has to be a dev build, because release CSP blocks the plugin's localhost fetch.
3. Settings → Plugins → Load from folder → examples/plugins/remote-ackbot, then enable it.
4. Agents → New agent → Remote ack bot (hosted). Add it to a channel and mention it.

The server answers only the app's and local pages' origins, and keeps its state file readable only by you. Keys are stored in plain text, so use it for testing only.

Testing

• Against a local relay: provision works and a bad attestation is rejected. Activate publishes the profile. An owner mention gets an "ack" in its thread. Delete is idempotent, and a foreign Origin gets 403.
• A mention stamped 2 s ahead of this clock with ms 900 got a reply in the same second with ms 901.

🤖 Generated with Claude Code

[baxen]

this is just a reference