🔧 How It Works
Each root node has a gateway. The gateway holds up to 10 channels, each connected to an external service. Depending on the channel direction, you can send content into your tree, have full conversations with it, or receive notifications like dream summaries, or all of the above.
Channels are configured per-root from the gateway management page. All secrets (bot tokens, webhook URLs, push subscriptions) are encrypted at rest.
📱 Channel Types
Three channel types are available today. More can be added as integrations are built for them.
💬
Telegram
Connects via a bot token and chat ID. Send messages to your tree, chat with it, or receive notifications, all through your Telegram chat or group.
🎮
Discord
Connects via a webhook URL or bot. Interact with your tree from a Discord channel or receive updates there.
🔔
Web Push
Browser push notifications. Works even when the tab is closed. Your browser will ask for permission when you add one. May need to be saved as a WEB APP to your phone's homescreen.
↔️ Direction
Each channel has a direction that controls which way data flows.
Input / Output
Full bidirectional connection. Talk to your tree, place data, or query it from external platforms like Discord and Telegram chatrooms. The tree responds back through the same channel. More platforms can and will be added, starting with the most important ones.
Output
The tree reaches out to you or external services with updates. Notifications like dream summaries and dream thoughts get pushed out. Used for alerts and keeping you informed without you having to check in. Web push channels are always output-only.
🎛️ Channel Modes
For channels with input capability, the mode controls what the AI can do when it receives a message. This maps to the same three interaction styles available in the web chat.
Place
The AI scans the tree for context, creates or edits nodes, but does not generate a response back. Use this for silent ingestion . Send content in and let the tree organize it.
Query
The AI reads the tree and generates a response, but cannot make any changes. Use this for safe read-only access. Ask questions without risk of modification.
Chat
Full tree chat. The AI reads the tree, can create or edit nodes, and generates a response. The same experience as the web chat interface.
Output-only channels don't use modes since they only push notifications outward. Modes become relevant when input channels are enabled.
🔔 Notification Types
Channels with output capability can subscribe to specific notification types. Only matching notifications are dispatched, so you can fine-tune what each channel receives. For example, one Discord channel for dream summaries only and another for everything.
dream-summary
dream-thought
More notification types will be added as new features are built, including contribution alerts, raw idea placements, and more.
🛡️ Queue Protection
Each input channel can process up to 2 messages at the same time. If a third message arrives while those are still running, the channel either responds with a busy message or stays silent, depending on the channel's queue behavior setting.
Respond (default) -- replies with "I'm already processing your last 2 messages. Please send again later."
Silent -- drops the overflow message without responding. Good for high-traffic channels where you don't want noise.
🚫 Cancel Command
Send cancel to any input channel to immediately abort all active processing on that channel. The tree stops whatever it was doing and replies "All active tasks cancelled." This is useful if you sent something by mistake or the AI is taking too long.
🎮 Discord Input
Discord output channels use a simple webhook URL (free for all tiers). Discord input channels require a Discord bot that maintains a persistent connection, so they are gated to Standard, Premium, and God tier subscribers. Telegram input channels are available to all tiers since they use lightweight HTTP webhooks.
⚙️ Managing Channels
Channels are managed from the gateway page on each root. You can:
Add a channel by choosing a type and direction, pasting in the connection details (bot token, webhook URL, or allowing browser notifications), and configuring its mode and notification subscriptions.
Test any channel with a single click to verify the connection works before relying on it.
Enable / Disable channels without deleting them. Disabled channels are skipped during dispatch.
Delete channels you no longer need. Only the user who created a channel can delete it.
Maximum 10 channels per root. All secrets are encrypted with AES-256-CBC using the same encryption key as custom LLM connections. The gateway API is also available programmatically. See the API Reference page for endpoints.