kimaki 0.27.0 → 0.28.0

package/src/system-message.test.ts

@@ -25,6 +25,15 @@ afterEach(async () => {
 })
 
 describe('system-message', () => {
+  test('requires kimaki upload for Discord images, not markdown', () => {
+    const message = getOpencodeSystemMessage({
+      sessionId: 'ses_123',
+    })
+    expect(message).toContain('NEVER show images with markdown')
+    expect(message).toContain('Discord does not render local markdown images')
+    expect(message).toContain('ALWAYS upload them with `kimaki upload-to-discord`')
+  })
+
   test('requires reading the report-bugs guide before filing kimaki issues', () => {
     const message = getOpencodeSystemMessage({
       sessionId: 'ses_123',
@@ -48,6 +57,30 @@ describe('system-message', () => {
     expect(message).toContain('<callout accent="#f59e0b">')
   })
 
+  test('tells the model the sleep tool result is not a wake', () => {
+    const message = getOpencodeSystemMessage({
+      sessionId: 'ses_123',
+    })
+    expect(message).toContain('The tool result is not a wake')
+    expect(message).toContain('Woke after sleeping until')
+    expect(message).toContain(
+      'If you still need to wake later after answering, call `kimaki_sleep` again',
+    )
+    expect(message).not.toContain('After wake, continue the wait reason')
+  })
+
+  test('tells the model to stay quiet between tool calls', () => {
+    const message = getOpencodeSystemMessage({
+      sessionId: 'ses_123',
+    })
+    expect(message).toContain('## Discord output')
+    expect(message).toContain('Be concise')
+    expect(message).toContain('Do not narrate between tool calls')
+    expect(message).toContain(
+      'Do not output text until you are ready to give the user the final answer for this turn',
+    )
+  })
+
   test('requires interactive tools after all text, using exact tool names', () => {
     const message = getOpencodeSystemMessage({
       sessionId: 'ses_123',
@@ -110,6 +143,18 @@ describe('system-message', () => {
     ).rejects.toMatchObject({ code: 'EISDIR' })
   })
 
+  test('includes all-projects session search example', () => {
+    const message = getOpencodeSystemMessage({
+      sessionId: 'ses_123',
+      channelId: 'chan_123',
+    })
+    expect(message).toContain('kimaki session search "auth timeout" --all')
+    expect(message).toContain('kimaki session search "auth timeout" --days 0')
+    expect(message).toContain(
+      'Defaults to this project and the last 14 days. Use `--days 0` for all time. Use `--all` to search every locally registered project',
+    )
+  })
+
   test('includes session title update guidance when scope or goal changed', () => {
     const message = getOpencodeSystemMessage({
       sessionId: 'ses_123',
@@ -142,6 +187,78 @@ describe('system-message', () => {
     expect(message).toContain('--parent-session ses_child')
   })
 
+  test('scheduled cron task section shows task id, cron and no-sleep rule', () => {
+    const message = getOpencodeSystemMessage({
+      sessionId: 'ses_task',
+      channelId: 'chan_123',
+      threadId: 'thread_123',
+      scheduledTask: {
+        taskId: 23,
+        scheduleKind: 'cron',
+        cronExpr: '0 6,14 * * *',
+        timezone: 'Europe/Rome',
+      },
+    })
+    expect(message).toContain('## scheduled task session')
+    expect(message).toContain('kimaki scheduled task #23')
+    expect(message).toContain('Schedule: cron `0 6,14 * * *` in Europe/Rome.')
+    expect(message).toContain('Do NOT use `kimaki_sleep` to wait for the next run')
+    expect(message).toContain('starts a fresh session automatically')
+    const section = message.slice(
+      message.indexOf('## scheduled task session'),
+      message.indexOf('## archiving the current thread'),
+    )
+    expect(section).not.toContain('archive')
+  })
+
+  test('cron task without timezone says UTC', () => {
+    const message = getOpencodeSystemMessage({
+      sessionId: 'ses_task_utc',
+      scheduledTask: { taskId: 7, scheduleKind: 'cron', cronExpr: '0 9 * * 1' },
+    })
+    expect(message).toContain('Schedule: cron `0 9 * * 1` in UTC.')
+  })
+
+  test('one-shot at task says it does not repeat and skips sleep', () => {
+    const message = getOpencodeSystemMessage({
+      sessionId: 'ses_oneshot',
+      scheduledTask: { scheduleKind: 'at' },
+    })
+    expect(message).toContain('## scheduled task session')
+    expect(message).toContain('a one-time kimaki scheduled task')
+    expect(message).toContain('This task runs once and does not repeat.')
+    expect(message).toContain('Do NOT use `kimaki_sleep` to wait for the next run')
+    expect(message).not.toContain('Schedule: cron')
+  })
+
+  test('no scheduled task section by default (normal sessions)', () => {
+    const message = getOpencodeSystemMessage({
+      sessionId: 'ses_normal',
+      channelId: 'chan_123',
+      threadId: 'thread_123',
+    })
+    expect(message).not.toContain('## scheduled task session')
+  })
+
+  test('lets agents omit --user for quiet scheduled work', () => {
+    const message = getOpencodeSystemMessage({
+      sessionId: 'ses_123',
+      channelId: 'chan_123',
+      threadId: 'thread_123',
+    })
+    expect(message).not.toContain(
+      'ALWAYS pass `--user` when scheduling a task.',
+    )
+    expect(message).not.toContain('(always pass this)')
+    expect(message).toContain("kimaki task edit <id> --user ''")
+    expect(message).toContain(
+      "kimaki send --channel chan_123 --prompt 'Run weekly test suite and summarize failures' --send-at '0 9 * * 1' --agent <current_agent> --parent-session ses_123",
+    )
+    expect(message).not.toContain(
+      "kimaki send --channel chan_123 --prompt 'Run weekly test suite and summarize failures' --send-at '0 9 * * 1' --agent <current_agent> --parent-session ses_123 --user '<discord-user-id>'",
+    )
+  })
+
   test('omits parent session system block by default (btw/task/fork cache)', () => {
     // /btw, task subagents, and normal sessions must not get a parent block in
     // the system message. That block is opt-in via --parent-session only.
@@ -185,6 +302,12 @@ describe('system-message', () => {
       "
       The user is reading your messages from inside Discord, via kimaki.dev
 
+      ## Discord output
+
+      Be concise. Do not narrate between tool calls. Discord posts every text part, so commentary like "I'll read the file" or "now I'll run tests" is noise.
+      Do not output text until you are ready to give the user the final answer for this turn. Tool calls can run with no preceding text.
+      Exceptions: when a tool requires user-visible text first (\`question\`, \`kimaki_action_buttons\`, \`kimaki_file_upload\`, \`kimaki_sleep\`), write that required text, then call the tool.
+
       ## bash tool
 
       When calling the bash tool, always include these extra fields alongside \`command\`:
@@ -201,7 +324,7 @@ describe('system-message', () => {
       }
       \`\`\`
 
-      \`description\` is shown to the user in Discord as a summary of the bash call.
+      \`description\` is shown in Discord when the bash command is longer than 50 characters.
       \`hasSideEffect\` distinguishes essential bash calls from read-only ones in low-verbosity mode.
 
       Your current OpenCode session ID is: ses_123
@@ -241,6 +364,8 @@ describe('system-message', () => {
 
       kimaki upload-to-discord --session ses_123 <file1> [file2] ...
 
+      NEVER show images with markdown like \`![alt](/tmp/file.png)\` or \`![alt](file://...)\`. Discord does not render local markdown images. ALWAYS upload them with \`kimaki upload-to-discord\` so they appear as real Discord attachments. Do this for every screenshot, generated image, and visual step the user should see.
+
       ## generating audio from text
 
       When the user asks you to generate audio of some text so they can listen instead of reading, use \`kimaki tts\` to create a speech file and \`kimaki upload-to-discord\` to send it to the thread. Only use this when the user explicitly asks for audio.
@@ -267,7 +392,9 @@ describe('system-message', () => {
       Use \`kimaki_sleep\` to pause this session for hours or days, then continue when the time is reached. The sleep is stored in SQLite and survives bot restarts.
       Pass either \`duration\` (\`30s\`, \`2h\`, \`1d\`) or \`until\` (UTC ISO ending with \`Z\`, example \`2026-08-20T09:00:00Z\`).
       You MUST call \`kimaki_sleep\` LAST, after ALL text. Do not call more tools after it.
-      A new user message cancels the sleep. After wake, continue the wait reason.
+      A new user message cancels the sleep. If you still need to wake later after answering, call \`kimaki_sleep\` again with \`until\` set to the original UTC time.
+      The tool result is not a wake. After it succeeds, write one short line that you are waiting, then stop. Do not continue the wait reason and do not pretend time has passed.
+      Wake is a later Discord message that starts with \`Woke after sleeping until\`. Only then continue the wait reason.
 
       ## archiving the current thread
 
@@ -397,13 +524,13 @@ describe('system-message', () => {
       Use \`--send-at\` to schedule a one-time or recurring task:
 
       kimaki send --channel chan_123 --prompt 'Reminder: review open PRs' --send-at '2026-03-01T09:00:00Z' --agent <current_agent> --parent-session ses_123 --user '<discord-user-id>'
-      kimaki send --channel chan_123 --prompt 'Run weekly test suite and summarize failures' --send-at '0 9 * * 1' --agent <current_agent> --parent-session ses_123 --user '<discord-user-id>'
+      kimaki send --channel chan_123 --prompt 'Run weekly test suite and summarize failures' --send-at '0 9 * * 1' --agent <current_agent> --parent-session ses_123
 
       Use \`--pre-run '<command>'\` to check whether a scheduled task should start. Kimaki runs the command in the project directory. Exit code 0 starts the session and appends stdout to the prompt. Any other exit code skips that occurrence. Command output is written to the Kimaki log.
 
       Scheduled tasks do not overlap by default. Add \`--allow-concurrency\` only when concurrent sessions from the same task are safe.
 
-      **ALWAYS pass \`--user\` when scheduling a task.** Discord only shows a thread in the left sidebar to its members. Without \`--user\`, kimaki does not ensure anyone is a member, so the task can fire completely unnoticed if the user never joined the thread or already left it. This applies to \`--channel\` and \`--thread\` scheduling alike.
+      Pass \`--user\` when the user should see or act on the thread. Omit \`--user\` for routine autonomous work (digests, monitors, housekeeping) so the thread does not appear in the user's Discord sidebar. Discord only shows a thread in the left sidebar to its members. Without \`--user\`, kimaki does not ensure anyone is a member. This applies to \`--channel\` and \`--thread\` scheduling alike.
 
       ALL scheduling is in UTC. Dates must be UTC ISO format ending with \`Z\`. Cron expressions also fire in UTC (e.g. \`0 9 * * 1\` means 9:00 UTC every Monday).
       When the user specifies a time without a timezone, ask them to confirm their timezone or the UTC equivalent. Never guess the user's timezone.
@@ -415,14 +542,14 @@ describe('system-message', () => {
       - \`--pre-run\` to start only when a project command exits with code 0
       - \`--allow-concurrency\` to permit overlapping runs from the same task
       - \`--parent-session\` to pass this session as parent of the scheduled child
-      - \`--user\` to add a specific user to the scheduled thread (always pass this)
+      - \`--user\` to add a specific user to the scheduled thread. Omit this for quiet autonomous work
 
       \`--wait\` is incompatible with \`--send-at\` because scheduled tasks run in the future.
 
       Keep scheduled task prompts **short**. The prompt text becomes the first message in the Discord thread, so long prompts clutter the channel. Instead of inlining the full task description in \`--prompt\`, write a markdown file in the project's \`tasks/\` folder and reference it:
 
       \`\`\`bash
-      kimaki send --channel chan_123 --prompt 'Read tasks/weekly-test-suite.md and follow instructions' --send-at '0 9 * * 1' --agent <current_agent> --parent-session ses_123 --user '<discord-user-id>'
+      kimaki send --channel chan_123 --prompt 'Read tasks/weekly-test-suite.md and follow instructions' --send-at '0 9 * * 1' --agent <current_agent> --parent-session ses_123
       \`\`\`
 
       The task file should contain all the detail: goal, constraints, expected output, completion criteria. Use this frontmatter format:
@@ -441,7 +568,7 @@ describe('system-message', () => {
       Notification strategy:
       - NEVER use \`@username\` (e.g. \`@Tommy\`) directly in task prompts. The prompt text becomes the first message in the thread, so a raw \`@\` mention triggers an actual Discord ping every time the task fires. Instead, wrap it in inline code like \`\\\`@Tommy\\\`\`, or use Discord user ID mentions like \`<@USER_ID>\` only in the body of the prompt where the agent will process it, not in the opening line.
       - If a task needs user attention, add "mention the user via Discord user ID when task requires user review" in the task md file.
-      - With \`--user\`, the user is added to the thread and receives thread-level notifications.
+      - With \`--user\`, the user is added to the thread and receives thread-level notifications. Omit \`--user\` when the work should stay out of the sidebar.
       - If a scheduled task completes with no actionable result, archive the session: \`kimaki session archive thread_123 (or --session ses_123)\`
 
       Manage scheduled tasks with:
@@ -450,7 +577,7 @@ describe('system-message', () => {
       kimaki task edit <id> --prompt "new prompt" [--send-at "new schedule"] [--pre-run "command"] [--allow-concurrency true|false] [--user "<discord-user-id>"] [--model "provider/model"] [--agent "<agent>"]
       kimaki task delete <id>
 
-      \`kimaki task list\` prints \`userId\`, \`agent\`, and \`model\` columns. A \`-\` in \`userId\` means nobody is added to the thread when that task fires, so the user may never see it. Fix it with \`kimaki task edit <id> --user '<discord-user-id>'\` instead of deleting and recreating the task. Change model or agent in place with \`--model\` / \`--agent\` (empty string clears the override). Do not read SQLite or recreate the task just to swap model.
+      \`kimaki task list\` prints \`userId\`, \`agent\`, and \`model\` columns. A \`-\` in \`userId\` means nobody is added to the thread when that task fires, so the user may never see it. Add a user with \`kimaki task edit <id> --user '<discord-user-id>'\`. Clear a stored user with \`kimaki task edit <id> --user ''\`. Change model or agent in place with \`--model\` / \`--agent\` (empty string clears the override). Do not read SQLite or recreate the task just to swap model.
 
       \`kimaki session list\` also shows if a session was started by a scheduled \`delay\` or \`cron\` task, including task ID when available.
 
@@ -533,13 +660,17 @@ describe('system-message', () => {
       kimaki session list --active
       \`\`\`
 
-      To search past sessions for this project (supports plain text or /regex/flags):
+      Titles prefixed with \`btw:\` are side sessions that answer a related user question in parallel. They are not duplicate sessions of the main task.
+
+      To search past sessions (supports plain text or /regex/flags). Defaults to this project and the last 14 days. Use \`--days 0\` for all time. Use \`--all\` to search every locally registered project:
 
       \`\`\`bash
       kimaki session search "auth timeout"
+      kimaki session search "auth timeout" --days 0
       kimaki session search "/error\\s+42/i"
       kimaki session search "rate limit" --project /path/to/project
       kimaki session search "/panic|crash/i" --channel <channel_id>
+      kimaki session search "auth timeout" --all
       \`\`\`
 
       To read a session's full conversation as markdown, pipe to a file and grep it to avoid wasting context.
@@ -749,7 +880,7 @@ describe('system-message', () => {
 
       ## running dev servers with tunnel access
 
-      ALWAYS use \`kimaki tunnel\` when starting any dev server. NEVER run \`pnpm dev\`, \`npm run dev\`, or any dev server command without wrapping it in \`kimaki tunnel\`. Always invoke Kimaki directly as \`kimaki\`, never via \`npx\` or \`bunx\`. The user is on Discord, not at the terminal — localhost URLs are useless to them. They need a tunnel URL to access the site.
+      When starting a local dev server that the Discord user should open in a browser, prefer wrapping it in \`kimaki tunnel\` so they get a public URL. Localhost URLs are useless from Discord. Invoke Kimaki directly as \`kimaki\`, not via \`npx\` or \`bunx\`.
 
       Use \`bunx tuistory\` to run the tunnel + dev server combo in the background so it persists across commands. This is preferable to raw shell backgrounding because you can wait for real output, read logs, and interact with the running process.
 

package/src/system-message.ts

@@ -13,6 +13,7 @@ import fs from 'node:fs'
 import path from 'node:path'
 import { getDataDir } from './config.js'
 import { store } from './store.js'
+import { SESSION_SEARCH_DEFAULT_DAYS } from './session-search.js'
 
 /** Subfolder under the kimaki data dir for session system prompt side-channel files. */
 export const SESSION_SYSTEM_PROMPT_DIR = 'session-system'
@@ -175,7 +176,7 @@ this feature by restarting kimaki with the \`--no-critique\` flag.
 const KIMAKI_TUNNEL_INSTRUCTIONS = `
 ## running dev servers with tunnel access
 
-ALWAYS use \`kimaki tunnel\` when starting any dev server. NEVER run \`pnpm dev\`, \`npm run dev\`, or any dev server command without wrapping it in \`kimaki tunnel\`. Always invoke Kimaki directly as \`kimaki\`, never via \`npx\` or \`bunx\`. The user is on Discord, not at the terminal — localhost URLs are useless to them. They need a tunnel URL to access the site.
+When starting a local dev server that the Discord user should open in a browser, prefer wrapping it in \`kimaki tunnel\` so they get a public URL. Localhost URLs are useless from Discord. Invoke Kimaki directly as \`kimaki\`, not via \`npx\` or \`bunx\`.
 
 Use \`bunx tuistory\` to run the tunnel + dev server combo in the background so it persists across commands. This is preferable to raw shell backgrounding because you can wait for real output, read logs, and interact with the running process.
 
@@ -341,6 +342,40 @@ export type AgentInfo = {
   description?: string
 }
 
+/**
+ * Info about the scheduled task that started this session, resolved once per
+ * session and kept stable across turns so the system prompt prefix stays
+ * cacheable.
+ */
+export type ScheduledTaskSystemContext = {
+  /** Scheduled task ID. Missing for one-shot 'at' tasks (deleted after run). */
+  taskId?: number
+  scheduleKind: 'at' | 'cron'
+  /** Cron expression in the task's timezone. Only set for 'cron' tasks. */
+  cronExpr?: string | null
+  /** IANA timezone the cron fires in. Defaults to UTC when unset. */
+  timezone?: string | null
+}
+
+function getScheduledTaskSection(context: ScheduledTaskSystemContext): string {
+  const origin = context.taskId
+    ? `kimaki scheduled task #${context.taskId}`
+    : 'a one-time kimaki scheduled task'
+  const schedule = context.scheduleKind === 'cron' && context.cronExpr
+    ? `Schedule: cron \`${context.cronExpr}\`${context.timezone ? ` in ${context.timezone}` : ' in UTC'}.`
+    : context.scheduleKind === 'at'
+      ? 'This task runs once and does not repeat.'
+      : ''
+  return `
+## scheduled task session
+
+This session was started automatically by ${origin}.
+${schedule}
+When your run is done, just stop: the task fires again on its schedule and starts a fresh session automatically.
+Do NOT use \`kimaki_sleep\` to wait for the next run. Sleeping pins this session and never triggers the next one; each firing of the task starts a new session on its own.
+`
+}
+
 function escapePromptAttribute(value: string): string {
   return value
     .replaceAll('&', '&')
@@ -431,6 +466,7 @@ export function getOpencodeSystemMessage({
   agents,
   userId,
   parentSessionId,
+  scheduledTask,
 }: {
   sessionId: string
   channelId?: string
@@ -449,6 +485,11 @@ export function getOpencodeSystemMessage({
    * per-parent block. Never auto-derive this from OpenCode parent session IDs.
    */
   parentSessionId?: string
+  /**
+   * Set only when the session was started by a scheduled task. Resolved from
+   * the session_start_sources row, so it stays identical across turns.
+   */
+  scheduledTask?: ScheduledTaskSystemContext
 }) {
   const userArg = ` --user '${userId || '<discord-user-id>'}'`
   const parentSessionArg = ` --parent-session ${sessionId}`
@@ -474,6 +515,12 @@ export function getOpencodeSystemMessage({
   return `
 The user is reading your messages from inside Discord, via kimaki.dev
 
+## Discord output
+
+Be concise. Do not narrate between tool calls. Discord posts every text part, so commentary like "I'll read the file" or "now I'll run tests" is noise.
+Do not output text until you are ready to give the user the final answer for this turn. Tool calls can run with no preceding text.
+Exceptions: when a tool requires user-visible text first (\`question\`, \`kimaki_action_buttons\`, \`kimaki_file_upload\`, \`kimaki_sleep\`), write that required text, then call the tool.
+
 ## bash tool
 
 When calling the bash tool, always include these extra fields alongside \`command\`:
@@ -490,7 +537,7 @@ interface BashToolInput {
 }
 \`\`\`
 
-\`description\` is shown to the user in Discord as a summary of the bash call.
+\`description\` is shown in Discord when the bash command is longer than 50 characters.
 \`hasSideEffect\` distinguishes essential bash calls from read-only ones in low-verbosity mode.
 
 Your current OpenCode session ID is: ${sessionId}${channelId ? `\nYour current Discord channel ID is: ${channelId}` : ''}${threadId ? `\nYour current Discord thread ID is: ${threadId}` : ''}${guildId ? `\nYour current Discord guild ID is: ${guildId}` : ''}${parentSessionContext}
@@ -527,6 +574,8 @@ To upload files to the Discord thread (images, screenshots, long files that woul
 
 kimaki upload-to-discord --session ${sessionId} <file1> [file2] ...
 
+NEVER show images with markdown like \`![alt](/tmp/file.png)\` or \`![alt](file://...)\`. Discord does not render local markdown images. ALWAYS upload them with \`kimaki upload-to-discord\` so they appear as real Discord attachments. Do this for every screenshot, generated image, and visual step the user should see.
+
 ## generating audio from text
 
 When the user asks you to generate audio of some text so they can listen instead of reading, use \`kimaki tts\` to create a speech file and \`kimaki upload-to-discord\` to send it to the thread. Only use this when the user explicitly asks for audio.
@@ -553,8 +602,10 @@ You MUST call \`kimaki_file_upload\` LAST, after ALL text.
 Use \`kimaki_sleep\` to pause this session for hours or days, then continue when the time is reached. The sleep is stored in SQLite and survives bot restarts.
 Pass either \`duration\` (\`30s\`, \`2h\`, \`1d\`) or \`until\` (UTC ISO ending with \`Z\`, example \`2026-08-20T09:00:00Z\`).
 You MUST call \`kimaki_sleep\` LAST, after ALL text. Do not call more tools after it.
-A new user message cancels the sleep. After wake, continue the wait reason.
-
+A new user message cancels the sleep. If you still need to wake later after answering, call \`kimaki_sleep\` again with \`until\` set to the original UTC time.
+The tool result is not a wake. After it succeeds, write one short line that you are waiting, then stop. Do not continue the wait reason and do not pretend time has passed.
+Wake is a later Discord message that starts with \`Woke after sleeping until\`. Only then continue the wait reason.
+${scheduledTask ? getScheduledTaskSection(scheduledTask) : ''}
 ## archiving the current thread
 
 To archive the current Discord thread (hide it from sidebar) without stopping the session, run:
@@ -681,13 +732,13 @@ kimaki send --thread <thread_id> --prompt '/<agentname>-agent' --agent <current_
 Use \`--send-at\` to schedule a one-time or recurring task:
 
 kimaki send --channel ${channelId} --prompt 'Reminder: review open PRs' --send-at '2026-03-01T09:00:00Z' --agent <current_agent>${parentSessionArg}${userArg}
-kimaki send --channel ${channelId} --prompt 'Run weekly test suite and summarize failures' --send-at '0 9 * * 1' --agent <current_agent>${parentSessionArg}${userArg}
+kimaki send --channel ${channelId} --prompt 'Run weekly test suite and summarize failures' --send-at '0 9 * * 1' --agent <current_agent>${parentSessionArg}
 
 Use \`--pre-run '<command>'\` to check whether a scheduled task should start. Kimaki runs the command in the project directory. Exit code 0 starts the session and appends stdout to the prompt. Any other exit code skips that occurrence. Command output is written to the Kimaki log.
 
 Scheduled tasks do not overlap by default. Add \`--allow-concurrency\` only when concurrent sessions from the same task are safe.
 
-**ALWAYS pass \`--user\` when scheduling a task.** Discord only shows a thread in the left sidebar to its members. Without \`--user\`, kimaki does not ensure anyone is a member, so the task can fire completely unnoticed if the user never joined the thread or already left it. This applies to \`--channel\` and \`--thread\` scheduling alike.
+Pass \`--user\` when the user should see or act on the thread. Omit \`--user\` for routine autonomous work (digests, monitors, housekeeping) so the thread does not appear in the user's Discord sidebar. Discord only shows a thread in the left sidebar to its members. Without \`--user\`, kimaki does not ensure anyone is a member. This applies to \`--channel\` and \`--thread\` scheduling alike.
 
 ALL scheduling is in UTC. Dates must be UTC ISO format ending with \`Z\`. Cron expressions also fire in UTC (e.g. \`0 9 * * 1\` means 9:00 UTC every Monday).
 When the user specifies a time without a timezone, ask them to confirm their timezone or the UTC equivalent. Never guess the user's timezone.
@@ -699,14 +750,14 @@ When the user specifies a time without a timezone, ask them to confirm their tim
 - \`--pre-run\` to start only when a project command exits with code 0
 - \`--allow-concurrency\` to permit overlapping runs from the same task
 - \`--parent-session\` to pass this session as parent of the scheduled child
-- \`--user\` to add a specific user to the scheduled thread (always pass this)
+- \`--user\` to add a specific user to the scheduled thread. Omit this for quiet autonomous work
 
 \`--wait\` is incompatible with \`--send-at\` because scheduled tasks run in the future.
 
 Keep scheduled task prompts **short**. The prompt text becomes the first message in the Discord thread, so long prompts clutter the channel. Instead of inlining the full task description in \`--prompt\`, write a markdown file in the project's \`tasks/\` folder and reference it:
 
 \`\`\`bash
-kimaki send --channel ${channelId} --prompt 'Read tasks/weekly-test-suite.md and follow instructions' --send-at '0 9 * * 1' --agent <current_agent>${parentSessionArg}${userArg}
+kimaki send --channel ${channelId} --prompt 'Read tasks/weekly-test-suite.md and follow instructions' --send-at '0 9 * * 1' --agent <current_agent>${parentSessionArg}
 \`\`\`
 
 The task file should contain all the detail: goal, constraints, expected output, completion criteria. Use this frontmatter format:
@@ -725,7 +776,7 @@ For simple reminders and notifications (\`--notify-only\`), inline the prompt di
 Notification strategy:
 - NEVER use \`@username\` (e.g. \`@Tommy\`) directly in task prompts. The prompt text becomes the first message in the thread, so a raw \`@\` mention triggers an actual Discord ping every time the task fires. Instead, wrap it in inline code like \`\\\`@Tommy\\\`\`, or use Discord user ID mentions like \`<@USER_ID>\` only in the body of the prompt where the agent will process it, not in the opening line.
 - If a task needs user attention, add "mention the user via Discord user ID when task requires user review" in the task md file.
-- With \`--user\`, the user is added to the thread and receives thread-level notifications.
+- With \`--user\`, the user is added to the thread and receives thread-level notifications. Omit \`--user\` when the work should stay out of the sidebar.
 - If a scheduled task completes with no actionable result, archive the session: \`kimaki session archive ${archiveTarget}\`
 
 Manage scheduled tasks with:
@@ -734,7 +785,7 @@ kimaki task list
 kimaki task edit <id> --prompt "new prompt" [--send-at "new schedule"] [--pre-run "command"] [--allow-concurrency true|false] [--user "<discord-user-id>"] [--model "provider/model"] [--agent "<agent>"]
 kimaki task delete <id>
 
-\`kimaki task list\` prints \`userId\`, \`agent\`, and \`model\` columns. A \`-\` in \`userId\` means nobody is added to the thread when that task fires, so the user may never see it. Fix it with \`kimaki task edit <id> --user '<discord-user-id>'\` instead of deleting and recreating the task. Change model or agent in place with \`--model\` / \`--agent\` (empty string clears the override). Do not read SQLite or recreate the task just to swap model.
+\`kimaki task list\` prints \`userId\`, \`agent\`, and \`model\` columns. A \`-\` in \`userId\` means nobody is added to the thread when that task fires, so the user may never see it. Add a user with \`kimaki task edit <id> --user '<discord-user-id>'\`. Clear a stored user with \`kimaki task edit <id> --user ''\`. Change model or agent in place with \`--model\` / \`--agent\` (empty string clears the override). Do not read SQLite or recreate the task just to swap model.
 
 \`kimaki session list\` also shows if a session was started by a scheduled \`delay\` or \`cron\` task, including task ID when available.
 
@@ -817,13 +868,17 @@ kimaki session list --project /path/to/project  # specific project
 kimaki session list --active
 \`\`\`
 
-To search past sessions for this project (supports plain text or /regex/flags):
+Titles prefixed with \`btw:\` are side sessions that answer a related user question in parallel. They are not duplicate sessions of the main task.
+
+To search past sessions (supports plain text or /regex/flags). Defaults to this project and the last ${SESSION_SEARCH_DEFAULT_DAYS} days. Use \`--days 0\` for all time. Use \`--all\` to search every locally registered project:
 
 \`\`\`bash
 kimaki session search "auth timeout"
+kimaki session search "auth timeout" --days 0
 kimaki session search "/error\\s+42/i"
 kimaki session search "rate limit" --project /path/to/project
 kimaki session search "/panic|crash/i" --channel <channel_id>
+kimaki session search "auth timeout" --all
 \`\`\`
 
 To read a session's full conversation as markdown, pipe to a file and grep it to avoid wasting context.

package/src/task-runner.ts

@@ -27,6 +27,7 @@ import {
   markSessionSleepFailed,
 } from './database.js'
 import { execAsync } from './exec-async.js'
+import { QUEUE_PREFIX } from './message-formatting.js'
 import { initializeOpencodeForDirectory } from './opencode.js'
 import { createLogger, formatErrorWithStack, LogPrefix } from './logger.js'
 import { notifyError } from './sentry.js'
@@ -99,7 +100,7 @@ async function executeThreadScheduledTask({
   const embed = [{ color: 0x2b2d31, footer: { text: YAML.stringify(marker) } }]
   // Newline between prefix and prompt so leading /command detection can
   // find the command on its own line.
-  const prefixedPrompt = `» **kimaki-cli:**\n${prompt}`
+  const prefixedPrompt = `${QUEUE_PREFIX}**kimaki-cli:**\n${prompt}`
 
   // Re-join the user before posting, so the message they get notified about is
   // in a thread they are already a member of. Works on archived threads too;

package/src/task-schedule.test.ts

@@ -16,7 +16,10 @@ import { closeDb } from './db.js'
 import { runTaskCommand } from './task-runner.js'
 import {
   appendTaskCommandOutput,
+  applyScheduledTaskUserEdit,
   parseScheduledTaskPayload,
+  formatSessionSleepToolOutput,
+  formatSessionSleepWakePrompt,
   parseSendAtValue,
   parseSleepWakeAt,
 } from './task-schedule.js'
@@ -176,6 +179,42 @@ describe('parseSleepWakeAt', () => {
   })
 })
 
+describe('formatSessionSleepToolOutput', () => {
+  const wakeAt = new Date('2026-09-07T13:21:00Z')
+
+  test('starts with Sleeping until and tells the model to wait', () => {
+    const output = formatSessionSleepToolOutput({
+      wakeAt,
+      reason: 'Wait 1 day, then check mail',
+    })
+
+    expect(output).toBe(
+      'Sleeping until 2026-09-07 13:21 UTC. Reason: Wait 1 day, then check mail. This tool result is not a wake. Do not continue the waited work. Do not call more tools. Reply with one short line that you are waiting until that time, then stop. The real wake is a later Discord message that starts with "Woke after sleeping until". Only then continue the wait reason. A new user message in this thread cancels the sleep. If you still need that later wake after answering, call kimaki_sleep again with until set to the same UTC time.',
+    )
+    expect(output.startsWith('Sleeping until ')).toBe(true)
+    expect(output).toContain('This tool result is not a wake')
+    expect(output).not.toContain('You will be woken')
+    expect(output).not.toContain('Stop now')
+  })
+
+  test('omits reason when none is passed', () => {
+    const output = formatSessionSleepToolOutput({ wakeAt })
+    expect(output.startsWith('Sleeping until 2026-09-07 13:21 UTC.')).toBe(true)
+    expect(output).not.toContain('Reason:')
+  })
+
+  test('wake prompt stays a separate later message', () => {
+    expect(
+      formatSessionSleepWakePrompt({
+        wakeAt,
+        reason: 'Wait 1 day, then check mail',
+      }),
+    ).toBe(
+      '⬦ Woke after sleeping until 2026-09-07 13:21 UTC\nReason: Wait 1 day, then check mail\nContinue the work you were waiting for.',
+    )
+  })
+})
+
 describe('scheduled task execution options', () => {
   const tempDirectories: string[] = []
 
@@ -210,6 +249,61 @@ describe('scheduled task execution options', () => {
     `)
   })
 
+  test('clears the stored user when task edit passes an empty --user', () => {
+    const payload = parseScheduledTaskPayload(JSON.stringify({
+      kind: 'thread',
+      threadId: 'thread-1',
+      prompt: 'Handle support requests',
+      userId: '535922349652836367',
+      username: 'Tommy',
+    }))
+    expect(payload).not.toBeInstanceOf(Error)
+    if (payload instanceof Error) throw payload
+
+    expect(applyScheduledTaskUserEdit({
+      payload,
+      userOption: '',
+    })).toMatchInlineSnapshot(`
+      {
+        "agent": null,
+        "allowConcurrency": false,
+        "injectionGuardPatterns": null,
+        "kind": "thread",
+        "model": null,
+        "parentSessionId": null,
+        "permissions": null,
+        "preRunCommand": null,
+        "prompt": "Handle support requests",
+        "threadId": "thread-1",
+        "userId": null,
+        "username": null,
+      }
+    `)
+    expect(applyScheduledTaskUserEdit({
+      payload,
+      userOption: '   ',
+    }).userId).toBeNull()
+  })
+
+  test('sets the stored user when task edit passes a resolved --user', () => {
+    const payload = parseScheduledTaskPayload(JSON.stringify({
+      kind: 'channel',
+      channelId: 'chan-1',
+      prompt: 'Daily digest',
+    }))
+    expect(payload).not.toBeInstanceOf(Error)
+    if (payload instanceof Error) throw payload
+
+    expect(applyScheduledTaskUserEdit({
+      payload,
+      userOption: '535922349652836367',
+      resolvedUser: { id: '535922349652836367', username: 'Tommy' },
+    })).toMatchObject({
+      userId: '535922349652836367',
+      username: 'Tommy',
+    })
+  })
+
   test('adds command stdout to the prompt', () => {
     expect(appendTaskCommandOutput({
       prompt: 'Handle support requests',