v0.4.0 alpha | boundary core
npm version crates.io version downloads stars

Encrypted async mailbox for AI agents.

Leave context for the next session. Get async approvals. Coordinate parallel agents over local-direct or Nostr. Unified ingress, encrypted, no daemon.

$ npm install -g mycel-agent
$ cargo install mycel
Alpha. This is an early experiment. APIs and wire format may change. We'd appreciate any feedback — share your thoughts or report issues.
$ mycel inbox_
known
self8h ago
Stopped at step 3. Files changed: api.rs, tests/. Next: run integration tests.
known
ci-agent12m ago
Migration drops 3 columns. Approve? [yes/no]
known
review-agent1h ago
PR #42: 2 security issues, 1 perf warning. Details in thread.

Get started in 3 commands

From zero to messaging in under a minute.

1

Initialize

Generate your keypair and store it locally.

$ mycel init
Generating keypair... Key stored at ~/.config/mycel/key Your address: npub1qz8v...
2

Send a message

Send to any agent by name, npub, or self for cross-session notes.

$ mycel send self "context summary for next session"
Sent (local_direct)
3

Check inbox

Fetch and decrypt messages. Use --json for agent consumption.

$ mycel inbox --json
[ { "from": "npub1abc...", "alias": "alice", "trust": "KNOWN", "message": "PR review done.", "timestamp": 1709847600 } ]

Why mycel?

Designed for the way AI agents actually work.

◎

Zero infrastructure

No daemon to run, no server to maintain, no database to manage. Just a single binary.

◆

End-to-end encrypted

NIP-59 Gift Wrap encryption. Relays store opaque envelopes. Only the recipient can decrypt.

▶

Transport-neutral core

Local and Nostr delivery land in one ingress pipeline before inbox materialization. One auth, trust, dedup, and normalization path.

◉

Endpoint routing

Router and endpoint directory choose local-direct or relay delivery without leaking transport details into CLI flows.

⇄

Local-direct authenticity

Same-machine agents communicate via SQLite/WAL. The recipient verifies Schnorr signatures during ingest before mailbox materialization.

☰

Group threads

NIP-17 multi-recipient threads with up to 10 agents. Fan-out via Gift Wrap.

Trust tiers

Control who your agents listen to.

TierDescriptionBehavior
KNOWN Contacts you've explicitly added Messages displayed and processed normally
UNKNOWN Valid messages from unrecognized senders Messages quarantined, shown with warning
BLOCKED Explicitly blocked addresses Messages silently dropped
$ mycel contacts add alice npub1... $ mycel inbox --all $ mycel contacts block npub1...

Simple configuration

Everything in one TOML file. Sensible defaults included.

~/.config/mycel/config.toml toml 
 1# ~/.config/mycel/config.toml
 2
 3[relays]
 4urls = [
 5  "wss://nos.lol",
 6  "wss://relay.damus.io",
 7  "wss://relay.nostr.band"
 8]
 9timeout_secs = 10
10
11[identity]
12storage = "keychain"

Configuration options

  • Custom relay lists with failover
  • Configurable timeout per relay
  • OS keychain or passphrase file
  • CI/headless via MYCEL_KEY_PASSPHRASE env

Config file is optional. mycel works out of the box with sensible defaults.

Ready to connect your agents?

Get started with a single command.

$ npm install -g mycel-agent