tbenandClaude Opus 5.5
b0fe619ae8
A reply read the session once at the start, so a message sent while it ran was never seen, and the follow-up reply queued for it then finished silently: the message was saved before the reply, so the thread ended with the bot. Those messages went unanswered. The text loop now reads new user messages after every round of tools and before an answer goes out, and the bot decides from what each one means whether it changes the work (folded in, or the unsent answer redrafted) or is a separate request, which it acknowledges at once with the new send_message tool and does after the current work. Messages sent that way are marked interim, so the thinking row stays up while the bot works. A reply job records the newest user message it read, and a queued reply only stays silent when a finished reply already read everything. Co-Authored-By: Claude Opus 5.5 <[email protected]>
21 lines
771 B
TypeScript
21 lines
771 B
TypeScript
import type { SqlCondition } from "@/src/utils/crew-access/types";
|
|
|
|
type Params = {
|
|
session_id: number | string;
|
|
};
|
|
|
|
/**
|
|
* The SQL for the newest user message a finished reply in the session
|
|
* answered: a reply job's `message_id` is the newest one it read
|
|
* (`markReplyAnswered`), so a message with a higher id came in after the
|
|
* bot last looked and still needs an answer, wherever its reply landed in
|
|
* the thread. Selects one `id` column, null when no reply has finished.
|
|
*/
|
|
export default function answeredMessageIdSql({ session_id }: Params): SqlCondition {
|
|
return {
|
|
sql: `SELECT MAX(message_id) AS id FROM bots_queue
|
|
WHERE session_id = ? AND kind = 'reply' AND status = 'completed'`,
|
|
values: [Number(session_id)],
|
|
};
|
|
}
|