Repository navigation
Feat/chat centric workspace - #318
Merged
Merged
Conversation
…ompletions The API already serves projects, artifacts, the model catalogue and chat completions; the frontend had no way to reach any of them. - ProjectsService, ArtifactsService and ModelsService for the three collections. - CompletionsService streams POST /chats/:chatId/completions over fetch, and reads the assembled context and triggers compaction. - ConversationsService holds the recent chats plus the team and project names that label them, so the shell and the screens share one list. - ChatRunsService owns in-flight runs across chats, so a generation survives navigation and its outcome can be flagged where it happened. - ModelCatalogService names the model an agent runs on.
Both collections are served by the API but had no screens. - /projects lists projects with their chat and artifact counts; a project's page shows its conversations and what they produced, read through the existing chats and artifacts endpoints filtered by projectId. - /artifacts lists what agents produced, filterable by title and type; an artifact's page shows its text content, links back to the chat, agent and project it came from, and opens file-backed content from the API. - A shared record-rows partial keeps rows consistent across both.
Rebuilds the shell and the chat screen around talking to agents, instead of treating chats as one section of an admin dashboard. Shell and navigation - The rail now leads with New chat and the four places work happens (Chats, Projects, Agents, Artifacts), and gives the rest of its height to the conversations: grouped by project, then by last activity, filterable, and marked while an agent is working, failed, or finished unseen. - Teams, shared memory, prompts, overview and spending move into a folded Workspace section, unfolded automatically while one of them is open. - The window opens on /chats/new. Cmd/Ctrl+N starts a chat; New agent moves to Cmd/Ctrl+Shift+A; the digit shortcuts follow the rail's order. - The trail names the open chat, project or team; the palette searches chats and offers the new destinations. Starting a chat - /chats/new is an empty conversation with the composer focused. Who the chat is with (agent with its model, or team) and its project are picked inline; the first message creates the chat, titles it from its first line, stores the turn and starts the reply. An owner that cannot reply is flagged before anything is sent. Replaces the create dialog. A conversation - Fills the window: a one-line header naming the participant and its model, a scrolling transcript on a reading measure, and a docked composer. - Replies stream in place with the agent's reasoning folded above them; an activity line says whether it is starting, reasoning or writing, with the elapsed time and the turn in a team run. Send becomes Stop while running. - Runs live in ChatRunsService, so they continue across navigation. Failures show the API's reason with Retry, and an unanswered turn offers to ask for the reply instead of retyping it. - Fenced code renders as copyable blocks; system and tool turns render as collapsible steps. Content is always bound as text. - Context, summary (with Compact now), the chat's artifacts and its facts move to a details panel toggled from a context gauge in the header. - Rename from the title, move between projects from the header.
…native menu - The native menu gains New Chat on CmdOrCtrl+N, matching the frontend, and New Agent moves to CmdOrCtrl+Shift+A so the accelerator no longer shadows it. - The web README lists the new surfaces and endpoints, explains how runs are owned and shown, and drops the notes that said the UI had no composer.
This was referenced Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
Closes #
How it was tested
Anything left out, or worth a second opinion
Checklist
npm run lint -w @glassbeetle/apipasses (API changes)npm testpassesnpm run buildpassesdocs/,README.md,apps/web/README.md)