tben
fcad4b49d6
The thinking row and the header menu both carry Stop while a bot has work open for the user anywhere: every pending or processing job of that bot in their conversations is failed as stopped, its task closed, a Stopped step recorded and one closing message posted per session, so the thread stops waiting and the bot goes idle. The handler running the job is aborted from this process through a registry, so a job stuck waiting on a model stops at once instead of on its next heartbeat, and a late face change after the abort is dropped. The release stage is now said in the app too: Settings > General reports "Cobble v0.1.5 (alpha)" next to development, and the README and RELEASING.md say what alpha means for installs.
95 lines
3.2 KiB
TypeScript
95 lines
3.2 KiB
TypeScript
import Row from "@moduletrace/twui/layout/Row";
|
|
import Span from "@moduletrace/twui/layout/Span";
|
|
import Stack from "@moduletrace/twui/layout/Stack";
|
|
import BotAvatar from "@/src/components/general/bot-avatar";
|
|
import botStoneProps from "@/src/utils/bot-stone-props";
|
|
import { BotGettingMessageStatusLine } from "@/src/dict/bot-queue-dict";
|
|
import type { BotWithLastMessage } from "@/src/types";
|
|
import botBusyState from "../(utils)/bot-busy-state";
|
|
import StopBotButton from "./stop-bot-button";
|
|
|
|
type Props = {
|
|
bot: BotWithLastMessage;
|
|
/**
|
|
* The latest step of the bot's active task.
|
|
*/
|
|
progress?: string | null;
|
|
/**
|
|
* The latest step of the reply running in this conversation.
|
|
*/
|
|
reply_progress?: string | null;
|
|
/**
|
|
* 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.
|
|
*/
|
|
has_task?: boolean;
|
|
};
|
|
|
|
/**
|
|
* 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. While it shows, a stop button pulls the plug on the bot's work.
|
|
*/
|
|
export default function BotThinkingRow({
|
|
bot,
|
|
progress,
|
|
reply_progress,
|
|
awaiting_reply,
|
|
receiving,
|
|
has_task,
|
|
}: Props) {
|
|
const name = bot.name || "The bot";
|
|
const { waiting, getting, thinking, working, busy, stoppable } = botBusyState({
|
|
bot,
|
|
awaiting_reply,
|
|
receiving,
|
|
has_task,
|
|
});
|
|
|
|
if (!busy) return null;
|
|
|
|
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 (
|
|
<Row role="status" className="w-full gap-3! flex-nowrap items-center">
|
|
<BotAvatar
|
|
image_media_id={bot.image_media_id}
|
|
{...botStoneProps({ color: bot.color, stone: bot.stone, hue: bot.hue })}
|
|
face={waiting ? "asleep" : "working"}
|
|
size={28}
|
|
/>
|
|
<Stack className="min-w-0 gap-0! items-start">
|
|
<Span className="text-sm leading-5 text-ink-secondary animate-pulse motion-reduce:animate-none">
|
|
{label}
|
|
</Span>
|
|
{detail ? (
|
|
<Span className="w-full text-xs leading-4 text-ink-secondary truncate">
|
|
{detail}
|
|
</Span>
|
|
) : null}
|
|
</Stack>
|
|
<StopBotButton bot_name={bot.name} disabled={!stoppable} />
|
|
</Row>
|
|
);
|
|
}
|