Question 1

How to use multiple models from a single OpenAI-compatible provider connection in Rakazo?

Accepted Answer

Upgrade to Rakazo v0.3.1+ (PR #1424), which added multi-model support per connection. Steps: 1) Go to Models settings and edit your OpenAI-compatible connection. 2) Click 'Find models' to auto-discover model IDs from the provider's /v1/models endpoint, or manually add model IDs (e.g., deepseek-v4.1-flash, glm-5.3, kimi-k3). 3) Enable the models you want; one remains the connection default. 4) Each bot, routine, helper, or backup can now independently select any enabled model from that connection, and individual task runs can override the bot's default model. Connections saved before this update keep working as a single-model list. Note: only enabled model IDs pass validation—unregistered IDs return 'Unknown model for that provider' errors.

Question 2

Why are chat messages invisible or disappearing in the app on iOS?

Accepted Answer

This bug was caused by the header blur overlay covering the message list, making sent messages and agent replies invisible. It was fixed in PR #1780 (together with #1683). To apply the fix, fully close the app and reopen it twice so the update loads, then retry the chat. Note: a separate issue where the keyboard covers the message input box on iOS 18 is addressed in PR #1862, which may not be merged yet.

Question 3

Why does a working bot show 'Waiting in line…' in the sidebar and have no Stop button in its own chat?

Accepted Answer

Two separate bugs cause this. Fix 1 — Wrong sidebar status: in `packages/db/src/thread-listing.ts`, `activeRunSelection` takes only the newest active run (`orderBy: createdAt desc, take: 1`), and consumers read `runs[0]`. A queued run created after a running one therefore wins and the badge reads 'Waiting in line…'. Fix: select more than one active run and pick the most advanced status (precedence: waiting > running > leased > queued), or order by status precedence instead of recency. Fix 2 — Missing Stop button: in `apps/api/src/thread-target.ts`, the bot branch (`target.kind === "bot"`) run query includes `trigger: { not: "bot_message" }`, which hides the bot's own delegated-work run, its live progress, and the Stop control. Fix: remove the `bot_message` trigger filter from the bot branch — it only belongs in the group branch where peer-bot runs exist. In a bot's own DM thread every run belongs to that bot (verified via SQL: zero runs where `thread.botId <> run.botId`), so nothing needs to be hidden.

Question 4

Why doesn't the approval card (ask block) show up when a bot requires tool approval during a bot-to-bot run?

Accepted Answer

This was a bug fixed in PR #1857. When you sent a message to a bot while it was still processing a bot-to-bot (peer) run with `trigger = bot_message`, your message was folded into that active peer run. Approval cards from peer runs were not rendered in the web UI, so the run sat in `waiting_input` with no visible prompt (e.g., a `schedule_create` "Review before schedule_create" ask block stayed hidden).

**Fix:** Update your self-hosted instance to a build that includes #1857. After the fix, a message sent while the bot is answering another bot no longer joins that bot-to-bot run — it waits and executes as its own user-triggered turn, so the approval card appears in the bot's chat normally.

**Workaround (older versions):** Stop the stuck `waiting_input` run via the API, then resend your message once the bot's peer run has finished so it starts a fresh `trigger = user` run, where approval cards render correctly.

Question 5

Why does my 'Every 30 days' (or 'Every N minutes/hours') schedule run at wrong intervals, like 1 day apart then a 58-day gap?

Accepted Answer

Cause: the scheduler converts interval presets into cron field steps (`*/45 * * * *`, `0 */15 * * *`, `0 0 */30 * *`). Cron steps are calendar-based, not elapsed-time-based, so they reset at each hour/day/month boundary. That makes 'Every 30 days' fire on Jan 31 and Feb 1, then nothing until Mar 31. Workaround until fixed: only use interval values that evenly divide their calendar field — minutes: divisors of 60 (5, 10, 15, 20, 30); hours: divisors of 24 (2, 3, 4, 6, 8, 12). For day-level recurrence, avoid 'Every N days' entirely and enter an explicit cron instead, e.g. `0 0 1 * *` for monthly on the 1st, or `0 0 * * *` for daily. Avoid presets like 45 minutes, 15 hours, or 30 days.

rakazo

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects