NNyquest docs

Moving Conversations Between Projects

Two ways to move a conversation: drag-and-drop, or right-click → Move to project.

Drag-and-drop

The fastest method on desktop:

  1. Open the conversation list (left sidebar in most chassis)
  2. Press and hold any conversation row
  3. Drag it onto a project row (in the project list, usually below conversations)
  4. Release — the conversation moves into the project

The conversation drops out of its previous location (top-level, or another project) and appears under the destination project.

Works across:

  • Top-level → project (most common)
  • Project → another project
  • Project → top-level (drop on the conversations header instead of a project row)

Right-click menu

If drag-drop is awkward (mobile, trackpad issues, accessibility):

  1. Right-click (or long-press on touch) the conversation row
  2. Click Move to project
  3. Pick the destination from the dropdown
  4. Confirm

Same end result. Slightly more clicks.

Bulk-move (multiple conversations)

Currently: one at a time. There's no multi-select for conversations yet.

If you need to bulk-move many conversations into a new project, the practical pattern is:

  • Create the project
  • Move conversations one by one (each takes ~1 second)
  • For 20+ conversations, ~30 seconds total — usually faster than building a bulk UI

A bulk-select feature is on the roadmap but not high priority.

What persists, what doesn't

When a conversation moves into a project, these persist:

  • Every message (yours + the model's) exactly as written
  • Artifacts already attached to the conversation
  • The conversation's title, timestamps, model used per message

These change going forward:

  • New messages in the conversation now use the destination project's system prompt
  • New artifacts created in the conversation belong to the destination project's vault
  • Memory recall now biases toward the destination project's other conversations

What if I move the wrong conversation?

Move it back. It's reversible — same drag-drop or right-click flow, in the other direction.

Drag-drop didn't work — what's wrong?

Possible causes:

  • Wrong target type. Dropping on the conversation list itself (instead of a specific project row) doesn't move; it's ambiguous. Drop directly on a project row.
  • Browser drag-drop disabled. Some Chrome flags disable HTML5 drag-drop. Toggle them off.
  • The conversation is locked. Conversations belonging to deleted/archived projects can't be drag-dropped (rare edge case). Use right-click instead.
  • Mobile: drag-drop isn't supported on touch devices in this version. Use the right-click (long-press) menu.

If something feels broken, talk to a real human.

Implementation note (for the curious)

The drag uses HTML5 drag-and-drop with a custom MIME type (application/x-nyquest-conv). The project rows accept the drop and fire PATCH /user/conversations/{id} with {"project_id": "..."} to the backend. The conversation list refreshes when the request completes.

Where to next