Initial commit: Discord-Claude Gateway with event-driven agent runtime
This commit is contained in:
@@ -148,3 +148,24 @@ Our approach: Since we use `--dangerously-skip-permissions`, the agent can run B
|
||||
5. Agent-managed tasks (dynamic scheduling)
|
||||
6. Conversation archiving (audit trail)
|
||||
7. Everything else as needed
|
||||
|
||||
---
|
||||
|
||||
## Completed: Config Simplification
|
||||
|
||||
Merged `soul.md`, `identity.md`, `user.md`, and `tools.md` into a single `CLAUDE.md` file. The config directory is now:
|
||||
|
||||
```
|
||||
config/
|
||||
├── CLAUDE.md ← Persona: identity, personality, user context, tools (all in one)
|
||||
├── agents.md ← Cron jobs + Hooks (parsed by gateway at startup)
|
||||
├── heartbeat.md ← Heartbeat checks (parsed by gateway at startup)
|
||||
├── memory.md ← Long-term memory (agent-writable, auto-created)
|
||||
└── sessions.json ← Channel → session ID map (auto-generated)
|
||||
```
|
||||
|
||||
Why this split:
|
||||
- `CLAUDE.md` is pure prompt context — the agent reads it but the gateway doesn't parse it
|
||||
- `agents.md` and `heartbeat.md` are parsed programmatically by the gateway to set up cron timers and heartbeat intervals
|
||||
- `memory.md` is the only file the agent writes to — keeping it separate prevents the agent from accidentally overwriting persona config
|
||||
- Fewer files to manage, one place to edit your persona
|
||||
|
||||
Reference in New Issue
Block a user