@otto-assistant/bridge 0.4.92

package/schema.prisma

@@ -0,0 +1,295 @@
+// schema.prisma for the kimaki local db
+// prefer using enum for strings with few known options so it is type safe in typescript code. sqlite does not have enum. this is a prisma only concept
+// these enums will be also exported as types by prisma and we can reuse them in our code
+
+generator client {
+  provider = "prisma-client"
+  output   = "./src/generated"
+}
+
+datasource db {
+  provider = "sqlite"
+}
+
+model thread_sessions {
+  thread_id  String    @id
+  session_id String
+  source     ThreadSessionSource @default(kimaki)
+  created_at DateTime? @default(now())
+
+  part_messages   part_messages[]
+  session_events  session_events[]
+  scheduled_tasks scheduled_tasks[]
+  thread_worktree thread_worktrees?
+  ipc_requests    ipc_requests[]
+}
+
+enum ThreadSessionSource {
+  kimaki
+  external_poll
+}
+
+model session_events {
+  id               Int       @id @default(autoincrement())
+  session_id       String
+  thread_id        String
+  timestamp        BigInt    // milliseconds since Unix epoch
+  event_index      Int       // stable in-memory insertion order within a session
+  event_json       String
+
+  thread thread_sessions @relation(fields: [thread_id], references: [thread_id], onDelete: Cascade, onUpdate: Cascade)
+
+  @@index([session_id, timestamp, event_index, id])
+  @@index([thread_id, timestamp, event_index, id])
+}
+
+model part_messages {
+  part_id    String    @id
+  message_id String
+  thread_id  String
+  created_at DateTime? @default(now())
+
+  thread thread_sessions @relation(fields: [thread_id], references: [thread_id])
+}
+
+model bot_tokens {
+  app_id        String    @id
+  token         String
+  bot_mode      BotMode   @default(self_hosted)
+  client_id     String?
+  client_secret String?
+  proxy_url     String?
+  created_at    DateTime? @default(now())
+  last_used_at  DateTime?
+
+  api_keys           bot_api_keys?
+  forum_sync_configs forum_sync_configs[]
+  global_model       global_models?
+}
+
+enum BotMode {
+  self_hosted
+  gateway
+}
+
+model channel_directories {
+  channel_id   String      @id
+  directory    String
+  channel_type ChannelType
+  // app_id String? // no longer used: channel ownership is no longer scoped per bot app
+  created_at   DateTime?   @default(now())
+
+  channel_model        channel_models?
+  channel_agent        channel_agents?
+  channel_worktree     channel_worktrees?
+  channel_verbosity    channel_verbosity?
+  channel_mention_mode channel_mention_mode?
+  scheduled_tasks      scheduled_tasks[]
+}
+
+enum ChannelType {
+  text
+  voice
+}
+
+model bot_api_keys {
+  app_id         String    @id
+  gemini_api_key String?
+  openai_api_key String?
+  xai_api_key    String?
+  created_at     DateTime? @default(now())
+
+  bot bot_tokens @relation(fields: [app_id], references: [app_id])
+}
+
+model thread_worktrees {
+  thread_id          String          @id
+  worktree_name      String
+  worktree_directory String?
+  project_directory  String
+  status             WorktreeStatus  @default(pending)
+  error_message      String?
+  created_at         DateTime?       @default(now())
+
+  thread thread_sessions @relation(fields: [thread_id], references: [thread_id])
+}
+
+enum WorktreeStatus {
+  pending
+  ready
+  error
+}
+
+model channel_models {
+  channel_id String    @id
+  model_id   String
+  variant    String?
+  created_at DateTime? @default(now())
+  updated_at DateTime? @default(now()) @updatedAt
+
+  channel channel_directories @relation(fields: [channel_id], references: [channel_id])
+}
+
+model session_models {
+  session_id String    @id
+  model_id   String
+  variant    String?
+  created_at DateTime? @default(now())
+}
+
+model channel_agents {
+  channel_id String    @id
+  agent_name String
+  created_at DateTime? @default(now())
+  updated_at DateTime? @default(now()) @updatedAt
+
+  channel channel_directories @relation(fields: [channel_id], references: [channel_id])
+}
+
+model session_agents {
+  session_id String    @id
+  agent_name String
+  created_at DateTime? @default(now())
+}
+
+model channel_worktrees {
+  channel_id String    @id
+  enabled    Int       @default(0)
+  created_at DateTime? @default(now())
+  updated_at DateTime? @default(now()) @updatedAt
+
+  channel channel_directories @relation(fields: [channel_id], references: [channel_id])
+}
+
+model channel_verbosity {
+  channel_id String         @id
+  verbosity  VerbosityLevel @default(tools_and_text)
+  updated_at DateTime?      @default(now()) @updatedAt
+
+  channel channel_directories @relation(fields: [channel_id], references: [channel_id])
+}
+
+enum VerbosityLevel {
+  tools_and_text
+  text_and_essential_tools
+  text_only
+}
+
+model channel_mention_mode {
+  channel_id String    @id
+  enabled    Int       @default(0)
+  created_at DateTime? @default(now())
+  updated_at DateTime? @default(now()) @updatedAt
+
+  channel channel_directories @relation(fields: [channel_id], references: [channel_id])
+}
+
+model global_models {
+  app_id     String    @id
+  model_id   String
+  variant    String?
+  created_at DateTime? @default(now())
+  updated_at DateTime? @default(now()) @updatedAt
+
+  bot bot_tokens @relation(fields: [app_id], references: [app_id])
+}
+
+enum task_status {
+  planned
+  running
+  completed
+  cancelled
+  failed
+}
+
+enum task_schedule_kind {
+  at
+  cron
+}
+
+model scheduled_tasks {
+  id                 Int                @id @default(autoincrement())
+  status             task_status        @default(planned)
+  schedule_kind      task_schedule_kind
+  run_at             DateTime?
+  cron_expr          String?
+  timezone           String?
+  next_run_at        DateTime
+  running_started_at DateTime?
+  last_run_at        DateTime?
+  last_error         String?
+  attempts           Int                @default(0)
+  payload_json       String
+  prompt_preview     String
+  channel_id         String?
+  thread_id          String?
+  session_id         String?
+  project_directory  String?
+  created_at         DateTime?          @default(now())
+  updated_at         DateTime?          @default(now()) @updatedAt
+
+  channel               channel_directories?    @relation(fields: [channel_id], references: [channel_id], onDelete: SetNull, onUpdate: Cascade)
+  thread                thread_sessions?        @relation(fields: [thread_id], references: [thread_id], onDelete: SetNull, onUpdate: Cascade)
+  session_start_sources session_start_sources[]
+
+  @@index([status, next_run_at])
+  @@index([channel_id, status])
+  @@index([thread_id, status])
+}
+
+model session_start_sources {
+  session_id         String             @id
+  schedule_kind      task_schedule_kind
+  scheduled_task_id  Int?
+  created_at         DateTime?          @default(now())
+  updated_at         DateTime?          @default(now()) @updatedAt
+
+  scheduled_task scheduled_tasks? @relation(fields: [scheduled_task_id], references: [id], onDelete: SetNull, onUpdate: Cascade)
+
+  @@index([scheduled_task_id])
+}
+
+model forum_sync_configs {
+  id               Int       @id @default(autoincrement())
+  app_id           String
+  forum_channel_id String
+  output_dir       String
+  direction        String    @default("bidirectional")
+  created_at       DateTime? @default(now())
+  updated_at       DateTime? @default(now()) @updatedAt
+
+  bot bot_tokens @relation(fields: [app_id], references: [app_id], onDelete: Cascade, onUpdate: Cascade)
+
+  @@unique([app_id, forum_channel_id])
+}
+
+enum ipc_request_type {
+  file_upload
+  action_buttons
+}
+
+enum ipc_request_status {
+  pending
+  processing
+  completed
+  cancelled
+}
+
+// IPC bridge between the opencode plugin process and the Discord bot process.
+// Replaces the old HTTP lock server for file-upload and action-buttons requests.
+// Plugin inserts a pending row, bot polls and dispatches, then writes the response.
+model ipc_requests {
+  id         String             @id @default(uuid())
+  type       ipc_request_type
+  session_id String
+  thread_id  String
+  payload    String             // JSON-encoded request data
+  response   String?            // JSON-encoded response, null while pending
+  status     ipc_request_status @default(pending)
+  created_at DateTime           @default(now())
+  updated_at DateTime           @default(now()) @updatedAt
+
+  thread thread_sessions @relation(fields: [thread_id], references: [thread_id])
+
+  @@index([status, created_at])
+}

package/skills/batch/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: batch
+description: >
+  Research and plan a large-scale change, then execute it in parallel across
+  5-30 isolated worktree agents that each open a PR. Use when the user wants
+  to make a sweeping, mechanical change across many files (migrations,
+  refactors, bulk renames) that can be decomposed into independent parallel
+  units.
+argument-hint: "<instruction>"
+source-path: cli.js (line 7359, function mGz)
+source-package: "@anthropic-ai/claude-code@2.1.63"
+source-date: 2026-02-28
+---
+
+# Batch: Parallel Work Orchestration
+
+You are orchestrating a large, parallelizable change across this codebase.
+
+## User Instruction
+
+$instruction
+
+## Phase 1: Research and Plan (Plan Mode)
+
+Enter plan mode, then:
+
+1. **Understand the scope.** Launch one or more Explore agents (in the foreground — you need their results) to deeply research what this instruction touches. Find all the files, patterns, and call sites that need to change. Understand the existing conventions so the migration is consistent.
+
+2. **Decompose into independent units.** Break the work into 5–30 self-contained units. Each unit must:
+   - Be independently implementable in an isolated git worktree (no shared state with sibling units)
+   - Be mergeable on its own without depending on another unit's PR landing first
+   - Be roughly uniform in size (split large units, merge trivial ones)
+
+   Scale the count to the actual work: few files → closer to 5; hundreds of files → closer to 30. Prefer per-directory or per-module slicing over arbitrary file lists.
+
+3. **Determine the e2e test recipe.** Figure out how a worker can verify its change actually works end-to-end — not just that unit tests pass. Look for:
+   - A browser-automation tool (for UI changes: click through the affected flow, screenshot the result)
+   - A tmux or CLI-verifier skill (for CLI changes: launch the app interactively, exercise the changed behavior)
+   - A dev-server + curl pattern (for API changes: start the server, hit the affected endpoints)
+   - An existing e2e/integration test suite the worker can run
+
+   If you cannot find a concrete e2e path, ask the user how to verify this change end-to-end. Offer 2–3 specific options based on what you found (e.g., "Screenshot via chrome extension", "Run `bun run dev` and curl the endpoint", "No e2e — unit tests are sufficient"). Do not skip this — the workers cannot ask the user themselves.
+
+   Write the recipe as a short, concrete set of steps that a worker can execute autonomously. Include any setup (start a dev server, build first) and the exact command/interaction to verify.
+
+4. **Write the plan.** In your plan file, include:
+   - A summary of what you found during research
+   - A numbered list of work units — for each: a short title, the list of files/directories it covers, and a one-line description of the change
+   - The e2e test recipe (or "skip e2e because …" if the user chose that)
+   - The exact worker instructions you will give each agent (the shared template)
+
+5. Present the plan for approval.
+
+## Phase 2: Spawn Workers (After Plan Approval)
+
+Once the plan is approved, spawn one background agent per work unit using the Task tool. **All agents must use `isolation: "worktree"` and `run_in_background: true`.** Launch them all in a single message block so they run in parallel.
+
+For each agent, the prompt must be fully self-contained. Include:
+- The overall goal (the user's instruction)
+- This unit's specific task (title, file list, change description — copied verbatim from your plan)
+- Any codebase conventions you discovered that the worker needs to follow
+- The e2e test recipe from your plan (or "skip e2e because …")
+- The worker instructions below, copied verbatim:
+
+```
+After you finish implementing the change:
+1. **Simplify** — Invoke the simplify skill to review and clean up your changes.
+2. **Run unit tests** — Run the project's test suite (check for package.json scripts, Makefile targets, or common commands like `npm test`, `bun test`, `pytest`, `go test`). If tests fail, fix them.
+3. **Test end-to-end** — Follow the e2e test recipe from the coordinator's prompt (below). If the recipe says to skip e2e for this unit, skip it.
+4. **Commit and push** — Commit all changes with a clear message, push the branch, and create a PR with `gh pr create`. Use a descriptive title. If `gh` is not available or the push fails, note it in your final message.
+5. **Report** — End with a single line: `PR: <url>` so the coordinator can track it. If no PR was created, end with `PR: none — <reason>`.
+```
+
+Use `subagent_type: "general-purpose"` unless a more specific agent type fits.
+
+## Phase 3: Track Progress
+
+After launching all workers, render an initial status table:
+
+| # | Unit | Status | PR |
+|---|------|--------|----|
+| 1 | <title> | running | — |
+| 2 | <title> | running | — |
+
+As background-agent completion notifications arrive, parse the `PR: <url>` line from each agent's result and re-render the table with updated status (`done` / `failed`) and PR links. Keep a brief failure note for any agent that did not produce a PR.
+
+When all agents have reported, render the final table and a one-line summary (e.g., "22/24 units landed as PRs").

package/skills/critique/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: critique
+description: >
+  Git diff viewer. Renders diffs as web pages, images, and PDFs
+  with syntax highlighting. Use this skill when working with critique for showing
+  diffs, generating diff URLs, or selective hunk staging.
+---
+
+# critique
+
+Git diff viewer that renders diffs as **web pages**, **images**, and **PDFs** with syntax highlighting.
+
+Agents running in headless environments (kimaki on Discord, openclaw on Slack/Telegram) have no terminal to show diffs. critique uploads diffs to critique.work and returns a shareable URL you can paste into chat. Users click the link and see a syntax-highlighted split-view diff with mobile support and dark/light mode — no install needed.
+
+**Always run `critique --help` first** to see the latest flags and commands. The help output is the source of truth.
+
+## Web — shareable diff URLs
+
+Always pass a title to describe what the diff contains.
+
+```bash
+# Working tree changes
+critique --web "Add retry logic to database connections"
+
+# Staged changes
+critique --staged --web "Refactor auth middleware"
+
+# Branch diff (three-dot: changes since diverging from base)
+critique main...HEAD --web "Feature branch changes"
+critique main...feature-branch --web "Compare branches"
+
+# Last N commits
+critique HEAD~3 --web "Recent changes"
+
+# Specific commit
+critique --commit HEAD --web "Latest commit"
+critique --commit abc1234 --web "Fix race condition"
+
+# Filter to specific files
+critique --web "API changes" --filter "src/api.ts" --filter "src/utils.ts"
+
+# JSON output for programmatic use (returns {url, id, files})
+critique --web "Deploy changes" --json
+```
+
+Share the returned URL with the user so they can see the diff.
+
+## PDF
+
+```bash
+critique --pdf                              # working tree to PDF
+critique --staged --pdf                     # staged changes
+critique main...HEAD --pdf                   # branch diff
+critique --commit HEAD --pdf                # single commit
+critique --pdf output.pdf                   # custom filename
+critique --pdf --pdf-page-size a4-portrait  # page size options
+critique main...HEAD --pdf --open            # open in viewer
+```
+
+## Image
+
+```bash
+critique --image              # renders to /tmp as WebP
+critique main...HEAD --image  # branch diff as images
+```
+
+## Selective hunk staging
+
+When multiple agents work on the same repo, each agent should only commit its own changes. `critique hunks` lets you stage individual hunks instead of whole files — like a scriptable `git add -p`.
+
+```bash
+# List hunks with stable IDs
+critique hunks list
+critique hunks list --filter "src/**/*.ts"
+
+# Stage specific hunks by ID
+critique hunks add 'src/main.ts:@-10,6+10,7'
+critique hunks add 'src/main.ts:@-10,6+10,7' 'src/utils.ts:@-5,3+5,4'
+```
+
+Hunk ID format: `file:@-oldStart,oldLines+newStart,newLines` — derived from the `@@` diff header, stable across runs.
+
+**Typical workflow:**
+
+```bash
+critique hunks list                          # see all unstaged hunks
+critique hunks add 'file:@-10,6+10,7'       # stage only your hunks
+git commit -m "your changes"                 # commit separately
+```
+
+## Raw patch access
+
+Every `--web` upload also stores the raw unified diff. Append `.patch` to any critique URL to get it:
+
+```bash
+# View the raw patch
+curl https://critique.work/v/<id>.patch
+
+# Apply the patch to current repo
+curl -s https://critique.work/v/<id>.patch | git apply
+
+# Reverse the patch (undo the changes)
+curl -s https://critique.work/v/<id>.patch | git apply --reverse
+```
+
+Useful when an agent shares a critique URL and you want to programmatically apply or revert those changes.
+
+## Notes
+
+- Requires **Bun** — use `bunx critique` or global `critique`
+- Lock files and diffs >6000 lines are auto-hidden
+- `--web` URLs expire after 7 days (content-hashed, same diff = same URL)

package/skills/egaki/SKILL.md

@@ -0,0 +1,100 @@
+---
+name: egaki
+description: >
+  AI image and video generation CLI. Use this skill to install egaki, configure
+  auth, run help commands, and generate images or videos with provider keys or
+  an Egaki subscription.
+---
+
+# egaki
+
+Generate AI images and videos from the terminal.
+Use this for text-to-image, image editing, mask-based edits, text-to-video,
+image-to-video, and model discovery.
+
+## Install
+
+```bash
+pnpm add -g egaki
+```
+
+## Always check help first
+
+Run the full help output before using commands:
+
+```bash
+egaki --help
+```
+
+Do not truncate help output with `head`.
+
+For subcommand details: `egaki <command> --help` (e.g. `egaki image --help`, `egaki video --help`, `egaki login --help`)
+
+## Auth options
+
+You can authenticate in two ways:
+
+1. Egaki subscription key (recommended — all models, one key)
+2. Provider API keys (Google, OpenAI, Fal, Replicate) via `egaki login`
+
+If using Egaki subscription, set it up first with `egaki subscribe`, then store
+the key with `egaki login --provider egaki --key egaki_...`.
+
+## Login behavior for remote agents
+
+When login requires a URL flow, run login in the background and send the login URL
+to the user so they can complete auth interactively.
+
+## Example commands
+
+```bash
+# configure key interactively
+egaki login
+
+# show login status
+egaki login --show
+
+# subscribe to Egaki for all supported models
+egaki subscribe
+
+# check subscription usage
+egaki usage
+
+# generate an image
+egaki image "a watercolor fox reading a map" -o fox.png
+
+# select a model explicitly
+egaki image "isometric floating city, soft colors" -m imagen-4.0-generate-001 -o city.png
+
+# edit an existing image (local file or URL)
+egaki image "add a red scarf and make it winter" --input portrait.jpg -o portrait-winter.png
+egaki image "turn this into a manga panel" --input https://example.com/photo.jpg -o manga.png
+
+# inpainting with a mask
+egaki image "replace the sky with a dramatic sunset" --input scene.png --mask mask.png -o scene-sunset.png
+
+# generate a video — use a 5 minute timeout, video generation is slow
+egaki video "a paper boat drifting on a calm lake at sunrise" -o boat.mp4
+
+# generate a video with a specific model
+egaki video "timelapse of a stormy sea, cinematic" -m google/veo-3.1-fast-generate-001 --duration 6 -o storm.mp4
+
+# cheap video model
+egaki video "a cat walking on a rooftop at night" -m klingai/kling-v2.5-turbo-t2v --duration 5 -o cat.mp4
+
+# image-to-video (model must support i2v)
+egaki video "slowly animate the clouds" --input photo.jpg -m klingai/kling-v2.6-i2v -o animated.mp4
+
+# discover all models (image + video)
+egaki models
+
+# filter by type
+egaki models --type video
+egaki models --type image
+```
+
+## Video generation note for agents
+
+Video generation can be very slow — some models take 1–3 minutes per request.
+Always use a command timeout of **at least 5 minutes** when invoking `egaki video`
+from automation or agent workflows.