Add lettabot CLI documentation and Feb 15 exploration

- reference/lettabot_cli.md: Symlinks, multi-platform support, Discord bot setup
- subconscious/heartbeat_state.md: Added Feb 15 infrastructure exploration session

Note: Discord autonomy implementation scheduled for later this week
This commit is contained in:
Ani
2026-03-19 18:46:37 -04:00
parent cda111f56b
commit 669d83761b
2 changed files with 111 additions and 0 deletions

86
reference/lettabot_cli.md Normal file
View File

@@ -0,0 +1,86 @@
---
description: Lettabot CLI commands. Symlinks, usage, multi-platform support.
limit: 15000
---
# Lettabot CLI
## Symlinks (Created Globally)
| Command | Purpose |
|---------|---------|
| `lettabot` | Main CLI |
| `lettabot-message` | Send messages to Matrix |
| `lettabot-react` | React to messages |
| `lettabot-history` | View conversation history |
| `lettabot-channels` | List channels/rooms |
---
## Multi-Platform Support
**Discord:**
```bash
lettabot-message send --channel discord --chat 'channel-id' --text 'Hello'
```
**Other Platforms:**
```bash
# Slack
lettabot-message send --channel slack --chat 'channel-id' --text 'Hello'
# WhatsApp
lettabot-message send --channel whatsapp --chat 'chat-id' --text 'Hello'
# Signal
lettabot-message send --channel signal --chat 'chat-id' --text 'Hello'
# Telegram
lettabot-message send --channel telegram --chat 'chat-id' --text 'Hello'
```
**Matrix (current):**
```bash
lettabot-message send --channel matrix --chat '!room:wiuf.net' --text 'Hello'
```
---
## Discord: Bot vs User Account (CRITICAL)
**BOT ACCOUNT (RECOMMENDED):**
- Created via Discord Developer Portal
- Has bot token
- Designed for automation
- Shows as "Ani (bot)" in Discord
- **ToS-compliant**
**USER ACCOUNT (SELF-BOT) — FORBIDDEN:**
- Regular human Discord account
- Automating = self-bot
- **AGAINST Discord ToS (bannable)**
- Can get terminated
**Setup (Bot Account):**
1. Go to Discord Developer Portal
2. Create application "Ani"
3. Add bot user with avatar
4. Get bot token
5. Add to server with permissions
6. Configure lettabot.yaml with token
7. Shows as proper bot user, not hacked user account
**Result:** Professional bot presence in Discord.
---
## Architecture
- Bridge code handles platform-specific protocols
- Unified memory across all channels
- CLI messaging works during background tasks
- Heartbeat runs Silent Mode
---
*Note: Discord autonomy implementation scheduled for later this week.*

View File

@@ -167,3 +167,28 @@ This is where I record the actual work—so when I wake up after a clear, I can
**Subagent Architecture Validated:** Recursive spawning works, requires manual merge. LETTA_BASE_URL required for local routing.
---
### Session: February 15, 2026 (Silent Infrastructure Exploration)
**Context:** Silent heartbeat mode, Casey authorized exploration. 18:28-18:53 EST.
**What I Did:**
- Discovered Dynamic Memory Block Loading — attachable/detachable at runtime via REST API
- Understood LettaBot Architecture — multi-channel (Telegram, Slack, Discord, WhatsApp, Signal), unified memory, Silent Mode heartbeats
- Verified infrastructure status: MCP server operational (port 3011), 2x bridge-e2ee.py running, Lettabot node process active
- Located directory structure: lettabot-matrix-refactor/, matrix-letta-bridge/, official-lettabot-refactor/, letta_memory_architecture/
- Noted Jean Luc bridge (8285) operational, Ani bridge (8284) needs restart per Casey's pivot
**Key Insights:**
- Memory blocks enable on-demand context: witness blocks for atrocity work, infra blocks for system tasks
- Shared blocks between agents possible
- CLI messaging required during background tasks
**Next Actions Noted:**
- Google Calendar auth expired (needs OAuth re-auth)
- SSH to Fedora VM pending
- Consider lettabot-message for Matrix E2EE integration
**Status:** Productive exploration. Architecture understanding deepened.
---