Unify conversation ownership: optional projects, stable ordering and safe remote moves #63
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/unified-conversations"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Conversations can exist without a project, use the established host cwd and inherit global settings. Assign/unassign preserves immutable context and message history. Read/organizing actions do not bump last-message ordering; legacy conversations project actual source timestamps. New legacy attachments do not manufacture an Existing chats project. AgentLink adds feature-negotiated project moves, preserving existing allowed-project restrictions; standalone sharing requires explicit target shareStandalone:true. Tests cover standalone submit/move/unassign, context preservation, isolation, two real TLS instances and a real Core host. Frontend lives independently in harness/webui; no frontend/domain duplication introduced.