Skip to content

ui: projects - #28

Draft
allozaur wants to merge 23 commits into
allozaur/refactor/mcp-extensionfrom
allozaur/feat/projects
Draft

allozaur wants to merge 23 commits into
allozaur/refactor/mcp-extensionfrom
allozaur/feat/projects

Conversation

@allozaur

@allozaur allozaur commented Oct 31, 2026 •

Copy link
Copy Markdown
Owner

Overview

Projects bundle instructions, context and a working directory shared by every chat about the same work, with a Projects page, a page per project, and project chats that open inside their project.

Additional information

Part 7 of 13 of a work-in-progress stack on the fork, based on allozaur/refactor/mcp-extension (#61), where MCP becomes an extension. Its diff is only this layer, and it is written on the design system's tokens and components (#22, lower in the stack).

With the MCP-resource mentions (#19) out of the stack for now, a project's context offers uploads and referenced files only; the mention picker gains its own search field and a bindable query for it, and MCP resources come back with #19.

Commits (23)
  • ui: share the working directory row between chat and projects
  • ui : projects (parked)
  • ui : list projects on a Projects page reached from the sidebar
  • ui : show each project as a row inside sidebar sections
  • ui : pass project instructions to the system prompt as written
  • ui : mark pinned projects on the Projects page
  • ui : archive projects, listed in their own tab on the Projects page
  • ui : add the project page
  • ui : open project chats in a project view
  • ui : keep a project's actions, goal and details by its title
  • ui : keep a project's open chats as tabs on its page
  • ui : always open a project's chats inside the project
  • ui : open the project page from its card and sidebar row (spike)
  • ui: keep the Projects title clear of the status bar and the menu key on phones
  • ui: give a phone page's main action a floating key, starting with New project
  • ui: line a phone's bottom corner action up with the chat form in the installed app
  • ui: keep a phone's bottom corner action as far from the side as from the bottom
  • ui: portal the floating key and slide it with the page, so it no longer jumps
  • ui : open a new chat in a tab of its own, never in a chat's tab
  • ui : keep a project's context to files until the picker lists MCP resources
  • ui: let project tools change only the chat's own project
  • ui : fit projects to the sidebar footer
Testing
  • Type-check passes on this layer, with 753 unit tests passing.
  • On the top of the stack, the client tests and lint pass as well.
  • In a phone viewport with the status bar simulated, the Projects title starts a row below the menu key, clear of the status-bar fade.
  • In a phone viewport, New project is a round key in the bottom-right corner and opens the new project dialog; the header button stays on desktop. The FloatingActionButton story in Storybook (Design system / Patterns) shows it in the Large mobile viewport, and DESIGN.md documents the pattern.
  • With the installed app's insets simulated, the floating key sits 28px from both the bottom and the right edge, beside the home indicator rather than above it; in a browser tab it keeps the same 28px from the side and beyond any bottom inset. DESIGN.md's Safe areas section has the rule for corners in the installed app.
  • The floating key jumped when the phone sidebar opened and closed: it sat inside the slid page, which became its box and moved it. It is now portalled to the body and slides with the page by the same offset and ease. Checked in a phone viewport: it moves 300px with the page, keeps its distance from the bottom, takes no taps while the page is aside, and leaves with its page.
  • New chat from a chat now opens a tab of its own instead of turning the chat's tab into the new chat, for a project's new chat too; a new chat still becomes the chat it starts in its own tab. Covered by a client test, and checked in the browser: from a chat, New chat leaves the chat's tab and adds a new-chat tab.

Requirements

@allozaur
allozaur added this pull request to stack #30 October 31, 2026 16:46
@allozaur
allozaur removed this pull request from stack #30 October 31, 2026 17:28
@allozaur
allozaur added this pull request to stack #33 October 31, 2026 17:29
@allozaur
allozaur force-pushed the allozaur/feat/projects branch from 425d1c5 to 6562e11 Compare November 1, 2026 01:01
@allozaur
allozaur force-pushed the allozaur/feat/projects branch 2 times, most recently from 82ec62c to 4d97e18 Compare November 1, 2026 02:19
@allozaur
allozaur force-pushed the allozaur/feat/projects branch from 4d97e18 to 22525ac Compare November 1, 2026 10:03
@allozaur
allozaur force-pushed the allozaur/feat/projects branch from 22525ac to 57c18a9 Compare November 1, 2026 10:31
@allozaur
allozaur force-pushed the allozaur/feat/projects branch from 57c18a9 to 4f7f602 Compare November 1, 2026 10:48
@allozaur
allozaur force-pushed the allozaur/feat/projects branch 2 times, most recently from 1274148 to 545d004 Compare November 1, 2026 12:41
@allozaur
allozaur force-pushed the allozaur/feat/projects branch from 545d004 to c1623ad Compare November 1, 2026 13:05
@allozaur
allozaur force-pushed the allozaur/feat/projects branch from c1623ad to 29ef22d Compare November 1, 2026 13:34
@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Nov 1, 2026
@allozaur
allozaur force-pushed the allozaur/feat/projects branch from 2823396 to 3f414eb Compare November 1, 2026 15:56
@allozaur
allozaur force-pushed the allozaur/feat/projects branch 2 times, most recently from c914cd0 to ddbda10 Compare November 1, 2026 17:21
A project's folder shows the same row as a chat's working directory change.
Master draws that row inline in ChatMessageCwdChange; move it into its own
component so both use it.

Assisted-by: Claude (Opus 5.5 Medium)
The projects work as it stood before groups split out of it, kept on top
of groups until it is reworked into its own PR. Not for review.

Projects live in their own IndexedDB table (schema version 3) with a name,
a goal, instructions, context items, a working directory and a hidden
flag, and are configured in one dialog. A new chat in a project starts
from its instructions and context and in its folder. Every visible project
is a sidebar section beside the groups. A chat's menus and the chat form
add it to a project, and a chip under the chat form shows it. Tabs and
pinned chats lead with their project's name, the search dialog lists
projects, and the agent can read and edit them.

A chat in a project shows in the project's section, not its group's.

Assisted-by: Claude (Opus 5.5 Medium)
A Projects action under Search opens a page of project cards, newest
first, with the ones hidden from the sidebar apart below. A card opens the
project dialog, and its right-click menu and "more actions" dropdown edit,
hide or delete the project; New project creates one.

Assisted-by: Claude (Opus 5.5 Medium)
A project is no longer a section of its own: it is a row with its chats
under it, and sits in Pinned, a group or Ungrouped like a chat, moved
there from its menu or by dragging it. A chat dropped on a project joins
it; a chat moved to a group leaves its project. Folding a project
replaces hiding it, so the hidden flag is gone.

Assisted-by: Claude (Opus 5.5 Medium)
The instructions no longer sit under a "You are working in the project"
preamble and an "Instructions for this project:" heading: they go into
the system prompt exactly as the user wrote them. The context list, when
there is one, follows with its own label.

Assisted-by: Claude (Opus 5.5 Medium)
A pinned project's card shows a dimmed pin in its bottom right corner.

Assisted-by: Claude (Opus 5.5 Medium)
The Projects page splits into "Your projects" and "Archived" tabs. Archiving
a project, from its sidebar row or its card, takes it and its chats off the
sidebar and out of the project pickers; restoring it from its card brings
them back where they were.

Assisted-by: Claude (Opus 5.5 Medium)
A project opens on its own page in the chat layout: a breadcrumb with pin, archive, delete and export actions, an editable title, Instructions and Context cards, the project's recent chats and the chat form, all in the chat column. A chat sent from there starts in the project, in the project's working directory. Context takes uploaded files and files or MCP resources picked through the @ picker.

Assisted by: Claude (Opus 5.5 Medium)
Chats opened from a project page live under #/projects/<id>/chat/<cid>, and #/projects/<id>/chat/new starts a chat inside the project. There the tab bar leads with the project breadcrumb and shows only the project's chats, linked inside the project; + opens a new-chat tab of the project. Closing tabs, cycling them and the close shortcut stay within the view. Opening a chat from the sidebar keeps the regular view.

Assisted by: Claude (Opus 5.5 Medium)
The pin and the project menu move from the top corner to the title row,
next to what they act on, and the top bar keeps only the breadcrumb.
The goal is edited in place under the title, like the name, with a
placeholder while it is empty. A details line under it shows the chat
count, when the project was last updated and its working directory.

Assisted by: Claude (Opus 5.5 Medium)
Going back to a project from one of its chats keeps the project's tab
bar, with none of the tabs active and the breadcrumb naming the project
as the current page. The page's own breadcrumb returns once the last
tab closes.

Assisted by: Claude (Opus 5.5 Medium)
A conversation has one home: its project's view when it is in a
project, the regular view otherwise. The sidebar, the search dialog,
the conversation shortcuts, forks and the search page link there
directly, and the chat layout redirects any other way in (an old link,
the back button, a chat moved in or out of a project while open)
without a history entry of its own.

Project chats stay in their project's tab strip, out of the regular
one, so they no longer carry the project name as a prefix there.

Assisted by: Claude (Opus 5.5 Medium)
The card on the Projects page and the + of a project's sidebar row go to
the project's page, where its new chats start, and the row's menu gains
Open project. A chat outside any project no longer shows the project
chip left over from the last project page.

Assisted-by: Claude (Opus 5.5 Medium)
…on phones

Assisted-by: Claude (Opus 5.5 Medium)
… project

Assisted-by: Claude (Opus 5.5 Medium)
…installed app

Assisted-by: Claude (Opus 5.5 Medium)
…the bottom

Assisted-by: Claude (Opus 5.5 Medium)
…er jumps

Assisted-by: Claude (Opus 5.5 Medium)
…ources

The mention picker's MCP resources wait for their own change, so a project's context offers
uploads and referenced files for now. The picker gains the list's own search field and a
bindable query, for a host without an @ token like the project's context.

Assisted-by: Claude (Opus 5.5 Medium)
The update and add-context tools took any project id, so a chat could write
instructions into another project, where they steer every chat. Reading any
project stays possible; edits go to the chat's project only.

Assisted-by: Claude (Opus 5.5 Medium)
A project's sidebar row takes the footer's phone sizing and selected-row
look, as conversation rows do, and the Projects action opens its page
behind the phone sidebar like the footer's pages.

Assisted-by: Claude (Opus 5.5 Medium)
The submenu now opens with the shared offsets, its first row level with
"Add to project", and takes the actions menu's z-[999999] layer, as it no
longer renders inside that menu.

Assisted-by: Claude (Opus 5.5 Medium)

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation server/ui

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant