Add the harness, envs, per-bot models and chat attachments
- Harness: providers, model catalog synced hourly, automatic free picks, cooldowns, tool loop with context trimming, MCP computer tools - Bots queue runs replies and tasks through the harness; jobs wait (attempt refunded) while every model is resting - Envs: Settings > Environment, scoped general/workspace/computer, written to computers and redacted from tool output - Models: Settings > Models, per-harness provider select defaulting to OpenRouter, and a models modal on each bot's chat (the coordinator's edits the defaults) - Chat: thinking row while a reply runs, file attachments (upload, paste, drop) that replies read as images, audio and document text - Fix media uploads failing after a user's first file, and private files being served from the public media path Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
@@ -0,0 +1,18 @@
|
||||
let wake: (() => void) | undefined;
|
||||
|
||||
/**
|
||||
* Lets the running queue handler register how to poll at once. Kept apart
|
||||
* from the handler so API routes can wake it without bundling it.
|
||||
*/
|
||||
export function setBotsQueueWaker({ waker }: { waker: () => void }) {
|
||||
wake = waker;
|
||||
}
|
||||
|
||||
/**
|
||||
* Polls now instead of at the next tick, so a chat reply starts at once.
|
||||
* Does nothing where the queue doesn't run (the next poll on the main
|
||||
* server picks the job up).
|
||||
*/
|
||||
export default function wakeBotsQueue() {
|
||||
wake?.();
|
||||
}
|
||||
Reference in New Issue
Block a user