Make Claude sessions optionally project-wide #11238
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
mtsgrd
force-pushed
the
claude-project-wide-sessions
branch
2 times, most recently
from
962faf6 to
60fed83
Compare
mtsgrd
changed the title
mtsgrd
force-pushed
the
claude-project-wide-sessions
branch
from
60fed83 to
740d1cd
Compare
The absence of a `stack_id` indicates the chat is project wide. In practical terms it just means the system prompt is slightly different, and at the end we don't try to create any commits.
mtsgrd
force-pushed
the
claude-project-wide-sessions
branch
from
740d1cd to
1fc1e6d
Compare
|
without a mechanism for distributing changes produced by claude to branches, i am not quite sure this fits the bill. I'd suggest leaving this for a future project looking at this more holistically (workspace sessions) |
|
Having slept on this I have an idea for how to make workspace-scoped chats work. If a stack or a branch is selected, a new commit is created there, if a commit is selected, then the new changes will be amended into that commit. This "target" can be changed between prompts and the context can be cleared on demand. The would require changing things up in how committing is done but it could be a nice UX. In any case, I would like to take this as a new project after we have shipped the current thing |
No description provided.