amosblomqvist
3e9a85d60f
The reported bug (2026-09-28): every chat ran glm-5.3-flash regardless of any pick, while composer and settings UIs agreed with each other and lied about the run. Root cause: a fossil default-settings record (settings.json chat section, frozen pre-slots-wave) was stamped verbatim into every new chat at birth by the new-session flow, and resolveConversationSpec prefers the per-chat record over the strong slot forever. Owner redesign — models are per session, always; the strong slot is the new-session default: - POST /api/chats stamps the newborn verbatim from the strong slot (model + thinking level); no client settings PUT on create anymore - the composer control is dual-bound: in-session it reads/writes the session's own record (GET /api/chats/:id, PUT .../settings); on the draft surfaces it binds the strong slot (picking there = changing the default) - thinking levels follow the identical mechanics (confirmed by owner) - the zombie default-settings system dies whole: useDefaultSettings, /api/settings/defaults, src/store/default-settings.ts, the chat section of UserSettings (sanitizer strips fossil copies), the legacy default-settings.json fold, and DEFAULT_SETTINGS_FILE - catalogDefaultsFor collapses to the strong slot alone - thinking display for a legacy unstamped session resolves exactly like the engine (session ?? strong ?? model ladder) Tests: new chat-birth-stamp suite pins the stamp, the unconfigured boot, the unset level, and the copy-not-live-view regression; defaults pins rewritten strong-only; legacy-migration suite deleted.
39 lines
1.8 KiB
TypeScript
39 lines
1.8 KiB
TypeScript
import { createChat, isTurnRunning, listChats, readSettingsRecord, stores, titleFromPrompt } from "@/src/server";
|
|
import type { ChatListItem } from "@/src/core";
|
|
|
|
/** The session picker's list: record-derived summaries (phase, pending
|
|
* question) + live liveness — a running turn marks the session busy
|
|
* (contracts.ts ChatListItem; the store can't see liveness, the route is
|
|
* the merge point). Owner, minimal-color round: background jobs NO LONGER
|
|
* count — the sidebar's Background agents section is their channel now
|
|
* (a running spinner per row would double-signal them), so busy means
|
|
* exactly "a teach turn is in flight". */
|
|
export async function GET() {
|
|
const chats: ChatListItem[] = listChats().map((c) => ({
|
|
...c,
|
|
busy: isTurnRunning(c.id),
|
|
}));
|
|
return Response.json({ chats });
|
|
}
|
|
|
|
export async function POST(req: Request) {
|
|
const body = (await req.json().catch(() => ({}))) as { title?: unknown };
|
|
const title = typeof body.title === "string" ? body.title : "";
|
|
const chat = createChat(titleFromPrompt(title || "Untitled session"));
|
|
// PER-SESSION MODELS (owner, 2026-09-28): a session owns its model +
|
|
// thinking level from birth — stamped verbatim from the STRONG slot,
|
|
// the new-session default. From here the strong slot never reaches
|
|
// this session again: in-session picks write the session's own record
|
|
// (PUT /api/chats/:id/settings). No strong slot configured (fresh BYOK
|
|
// boot) → no stamp; the turn gate's 503 models_not_configured envelope
|
|
// refuses honestly until the setup flow fills the slot.
|
|
const strong = readSettingsRecord()?.models?.strong;
|
|
if (strong?.model) {
|
|
stores.chatStore.saveSettings(chat.id, {
|
|
model: { provider: strong.model.provider, id: strong.model.id },
|
|
thinkingLevel: strong.thinkingLevel,
|
|
});
|
|
}
|
|
return Response.json({ id: chat.id, title: chat.title });
|
|
}
|