Moduletrace/cobble
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 32 Wiki Activity

Show sent messages before the server confirms them

Browse Source 
The composer now puts the bubble and clears the input as soon as you send, so a slow connection never holds either. The bot's status row reads "<name> is getting your message..." until the saved message arrives (by response or push), then switches to thinking. A failed send removes the bubble and restores the text and files.
This commit is contained in:
tben
2026-10-20 14:50:20 +01:00
parent 4f7e0a6bf0
commit 8425631b3a
9 changed files with 323 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/pages/admin/bots/[bot_id]/(partials)/bot-thinking-row.tsx
+32 -15
View File
@@ -5,6 +5,7 @@ import BotAvatar from "@/src/components/general/bot-avatar";
import type { BotHue } from "@/src/dict/bot-dict";
import {
BotComputerBusyStatusLine,
BotGettingMessageStatusLine,
BotReplyJobTitle,
BotWaitingStatusLine,
} from "@/src/dict/bot-queue-dict";
@@ -24,6 +25,11 @@ type Props = {
* The thread's last message is the user's, so a reply is due here.
*/
awaiting_reply?: boolean;
/**
* The user's last message is still on its way to the server, so the bot
* hasn't got it yet.
*/
receiving?: boolean;
/**
* This session has an active task.
*/
@@ -31,32 +37,43 @@ type Props = {
};
/**
* Under the last message while the bot is working on a reply or a task
* (or waiting for a model or its computer), so slow work doesn't look like
* none. A task or a reply shows its latest step. The bot's face is one per user,
* shared by all their sessions with it, so a reply shows from the thread
* alone: every user message queues one, so while the user has the last
* word a reply is due here, even while the bot works elsewhere. Only the
* waits (for a model, for its computer) come from the face.
* Under the last message while the bot is getting a just-sent message,
* working on a reply or a task (or waiting for a model or its computer), so
* slow work doesn't look like none. A task or a reply shows its latest step.
* The bot's face is one per user, shared by all their sessions with it, so a
* reply shows from the thread alone: every user message queues one, so while
* the user has the last word a reply is due here, even while the bot works
* elsewhere. Only the waits (for a model, for its computer) come from the
* face.
*/
export default function BotThinkingRow({ bot, progress, reply_progress, awaiting_reply, has_task }: Props) {
export default function BotThinkingRow({
bot,
progress,
reply_progress,
awaiting_reply,
receiving,
has_task,
}: Props) {
const name = bot.name || "The bot";
const asleep = bot.face == "asleep";
const waiting_model = asleep && bot.status_line == BotWaitingStatusLine && Boolean(awaiting_reply || has_task);
const waiting_computer =
asleep && bot.status_line == BotComputerBusyStatusLine && Boolean(has_task) && !awaiting_reply;
const waiting = waiting_model || waiting_computer;
const thinking = Boolean(awaiting_reply) && !waiting;
const getting = Boolean(receiving) && Boolean(awaiting_reply);
const thinking = Boolean(awaiting_reply) && !waiting && !getting;
const working =
!awaiting_reply && bot.face == "working" && bot.status_line != BotReplyJobTitle && Boolean(has_task);
if (!thinking && !working && !waiting) return null;
if (!getting && !thinking && !working && !waiting) return null;
const label = thinking
? `${name} is thinking…`
: working
? `${name} is working…`
: `${bot.status_line}…`;
const label = getting
? `${name} is ${BotGettingMessageStatusLine.toLowerCase()}…`
: thinking
? `${name} is thinking…`
: working
? `${name} is working…`
: `${bot.status_line}…`;
const detail = working ? progress : thinking ? reply_progress : null;
return (