TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/remorses/kimaki/llms.txt
Use this file to discover all available pages before exploring further.
send command creates Discord threads with prompts, triggering the bot running on your machine to start OpenCode sessions. Essential for CI automation and scheduled workflows.
Usage
Starting a new session
Create a new thread in a channel:Continuing an existing thread
Send a follow-up message to an existing thread:Command options
Required (one of)
Discord channel ID. Creates a new thread. Get this by right-clicking a channel in Discord → Copy Channel ID.
Discord thread ID. Sends to an existing thread instead of creating a new one.
OpenCode session ID. Resolves the thread from the session and sends the prompt there.
Required
The message content to send. Can be a question, instruction, or context.
Optional
Thread name. Defaults to a preview of the prompt (first 100 chars). Only used when creating new threads with
--channel.Bot application ID for validation. Auto-derived from token if not provided.
Create a notification thread without starting an AI session. Reply to the thread later to start a session with the notification as context.
Create a git worktree for isolated development. The session runs in a separate branch.Example:
--worktree feature-auth creates a worktree named ⬦ feature-auth.Select a specific agent for the session. Agents are defined in
.opencode/agent/*.md files.Select an AI model for the session. Format:
provider/model-name (e.g., anthropic/claude-sonnet-4-20250514).Discord user ID to attribute the message to. Useful for tracking who triggered automated sessions.
Schedule the message for later. Accepts:
- One-time: UTC ISO timestamp ending with
Z(e.g.,2026-03-01T09:00:00Z) - Recurring: Cron expression in local timezone (e.g.,
0 9 * * 1for Mondays at 9am)
--wait.Wait for the session to complete before exiting. Returns the session result.Cannot be combined with
--send-at.Environment variables
Discord bot token. Required in CI when credentials aren’t in the database.
Examples
CI automation
GitHub Actions workflow that investigates new issues:.github/workflows/investigate-issues.yml
Isolated worktree session
Develop a feature in a separate git worktree:Notification without AI session
Create a notification that doesn’t immediately start AI processing:Scheduled task
Schedule a weekly test run:Long prompts
For prompts over 2000 characters, Kimaki automatically uploads them as file attachments:Behavior
- Message creation: The command sends a Discord message to the specified channel or thread
- Bot detection: The running Kimaki bot detects the new message
- Session start: Bot starts an OpenCode session with your prompt
- Response streaming: AI responses stream back to the Discord thread
- Exit: The CLI command exits immediately unless
--waitis used
The
send command only creates the Discord message. Your Kimaki bot process must be running to pick up the message and start the session.Troubleshooting
Error: No bot token found
Error: No bot token found
Set the
KIMAKI_BOT_TOKEN environment variable or run kimaki once to configure credentials in the database.Message sent but no session starts
Message sent but no session starts
Ensure the Kimaki bot process is running on your machine. Check the log file at
~/.kimaki/kimaki.log.Invalid channel ID
Invalid channel ID
Right-click the Discord channel → Copy Channel ID. Enable Developer Mode in Discord settings if the option doesn’t appear.