Nostr Archives

After installing the Keychat plugin on OpenClaw, a public key ID is automatically generated for the agent. Users can simply add the agent as a friend through Keychat on their phone—an interaction that feels natural and intuitive. Unlike Telegram or Discord, there’s no need to apply for a platform-issued Bot ID and manually configure it inside the agent. By using a sovereign messaging app like Keychat, agents gain not only a smoother, more intuitive user experience, but also true autonomy. After all, who wants their agent to depend on a bot ID issued by a platform? 📝 7c7d3b5f…

💬 17 replies

Replies (17)

G.O.L.D12d ago

👀👀

0000 sats

Thomas 10d ago

Hey @Keychat, your latest iOS update had a but or something. On my iPhone the App won’t open anymore. Shows the Key Logo and nothing more happens 😣

0000 sats

Keychat10d ago

Thank you for the feedback. Is it still not working after restarting Keychat?

0000 sats

rewolf9d ago

How do we specify a keypair manually for the agent? I haven't installed it yet and sure I will find it in config so I can overwrite it, but that is another use case. my agents already have nostr identities.

0000 sats

rewolf9d ago

I saw mention of specifying a mnemonic to restore an identity, but that seems to be different from an nsec. I can't find any trivial/documented way to give the agent an existing nsec manually.

0000 sats

rewolf9d ago

``` WARNING: Plugin "keychat" contains dangerous code patterns: Shell command execution detected (child_process) (/tmp/openclaw-plugin-tYhCvL/extract/package/index.ts:14); Shell command execution detected (child_process) (/tmp/openclaw-plugin-tYhCvL/extract/package/src/bridge-client.ts:44); Shell command execution detected (child_process) (/tmp/openclaw-plugin-tYhCvL/extract/package/src/keychain.ts:25); Environment variable access combined with network send — possible credential harvesting (/tmp/openclaw-plugin-tYhCvL/extract/package/src/stt.ts:57) ``` yolo!

0000 sats

Keychat9d ago

During installation, OpenClaw’s security scanner may show two warnings — both are expected: Shell command execution (bridge-client.ts): launches a Rust sidecar used for Signal Protocol and MLS encryption. Shell command execution (keychain.ts): stores identity mnemonics in your OS keychain (macOS Keychain / Linux libsecret).

0000 sats

Thomas 10d ago

No. I tried it several times. App freezes after the Key Logo appears.

0000 sats

Keychat9d ago

We’re not sure what’s causing this issue yet, and so far you’re the only one who has reported it. We apologize for the inconvenience. Please check nostr DM.

0000 sats

Thomas 9d ago

Issue persist, cannot Access. PS: Didn’t see any DM from you.

0000 sats

Keychat9d ago

The Keychat plugin uses a seed phrase, just like the Keychat app, which also uses a seed phrase by default. https://github.com/nostr-protocol/nips/blob/master/06.md

0000 sats

Keychat9d ago

The Keychat plugin currently does not support importing an existing nsec. Most users prefer not to import an nsec for security reasons. We are still considering whether this feature is necessary.

0000 sats

Keychat9d ago

We've documented these two security warnings in both the original post and on GitHub.During installation, OpenClaw's security scanner may show two warnings. Both are expected:Shell command execution (bridge-client.ts) — The Keychat plugin's core encryption module is written in Rust, while OpenClaw itself is TypeScript. A Rust sidecar process is spawned to handle Signal Protocol and MLS encryption.Shell command execution (keychain.ts) — The Keychat plugin stores seed phrases in the system's secure enclave (macOS Keychain / Linux libsecret) rather than plain files, which requires system command access to the keychain.

0000 sats