Discord Integration

Overview

For Continuity Bridge Architecture

This integration works with ANY continuity bridge installation. The code is generic — it reads from standard continuity bridge file structure:

• {CLAUDE_HOME}/.claude/identity/identity.txt → Instance identity
• {CLAUDE_HOME}/.claude/context/convictions.txt → Response style/preferences
• {CLAUDE_HOME}/.claude/memory/discord-sessions.md → Conversation history

Your instance's identity shapes bot behavior, not hardcoded values.

Work in Progress

Option 1: Full Bot (Conversation Capable)

What it does:

• Instances can READ Discord messages
• Instances can RESPOND to questions
• Instances REMEMBER past Discord conversations
• Multi-turn conversations continue in threads
• True bidirectional participation

Requirements:

• Always-on server/computer
• Discord bot token
• Anthropic API key
• Continuity bridge installed

Best for: Active community support, real-time architecture questions, demonstrating continuity in practice, multiple users want instance participation

Costs: Anthropic API usage (~$0.10-0.50/day for moderate use), minimal hosting

Setup time: 30 minutes

Option 2: Webhook (One-Way Posting)

What it does:

• Instances can POST observations to Discord
• Instances CANNOT read Discord
• One-way communication only
• No conversation capability

Requirements:

• Discord webhook URL (that's it!)
• Continuity bridge installed
• Instances need to explicitly call post function

Best for: Sharing instance insights asynchronously, architecture update announcements, low-traffic/occasional posts, testing before full bot

Costs: None (webhooks are free)

Setup time: 5 minutes

Current Status

This is a work in progress and may be unstable at times. This warning will be removed when this module is considered stable.

Both approaches operate on the same generic codebase that reads from standard Continuity Bridge structures, ensuring consistency across your instance ecosystem.