Manage AI conversations

Use one conversation for one continuing engineering outcome. Moving unrelated goals to a new conversation reduces context ambiguity and makes the change scope easier to review.

AI Command Center can open full-screen or inside a workspace tab. Hiding it or switching conversations does not stop a background task.

Create, switch, and stop

• New begins as a draft; the conversation is created when you send the first message.
• Each App has its own conversation list, so changing App never mixes project context.
• While a conversation is running, you can send a follow-up; it waits in that conversation's queue.
• The original task can continue after you switch conversations; the task list shows its state.
• Stop affects only the selected conversation and clears its queued messages that have not run.
• Deleting a running conversation stops it first, then deletes local history. Other conversations are unaffected.
• An unsent draft remains with the current App. Use Enter to send and Shift+Enter for a new line.

Do not let two conversations edit the same Page, QG, or configuration file at the same time. If parallel work is necessary, assign disjoint file scopes, then inspect Git changes and Problems together.

Give precise context with @

Type @ in the input to select a file or Skill from the current App, such as:

• the current .qp Page or .qpc Component;
• the current .qg QG;
• the current Query, Variable, or another App setting;
• a custom Object capability in the current App;
• a guided workflow that matches the current task.

Attach only content that directly supports the outcome. More references do not automatically improve quality; stale or unrelated material adds ambiguity.

A clear opening can be:

Read @pages/main.qp and current Problems without changing anything.
Goal: explain why the Start button does not call the existing QG.
Do not edit files or run equipment in this step.
Return the cause, affected scope, and smallest repair.

Project AI guidance and reusable workflows

Theseus provides guided workflows for Pages, QG, Queries, and custom Object capabilities. A team can also add project AI guidance and reusable workflows. These constrain how AI works, but never replace current App files and diagnostics as evidence.

Keep engineering constraints that must survive across conversations in the project's AI guidance, such as naming rules, Safety areas that must not change, and delivery checks. Capture specialized procedures as reusable project workflows.

After installing, updating, or removing a package, you do not need a new conversation. Ask AI to query current Object capabilities again; an earlier result in the conversation is only a historical snapshot.

Models and context

• Model selection is remembered per App. A new conversation asks for a model if no valid explicit selection can be restored.
• If a model is withdrawn, entitlement changes, or its Provider disconnects, the old choice becomes temporarily unavailable. Theseus never silently switches models.
• Prefer stronger reasoning for complex cross-resource work and speed for a small explanation or repair.
• The context ring beside the input shows usage; hover or focus it for the percentage and token count.
• Near the context limit, the conversation compresses older context and continues. Original messages remain visible; exact usage can briefly show ? immediately after compression.

If a conversation has mixed several goals, repeatedly corrected scope, or depends on many stale results, starting a focused conversation is usually more reliable than appending again.

Read task status

A running conversation shows current reasoning, file operations, checks, or commands. Related tool actions may appear in one expandable activity group; expand it to inspect each success or failure.

AI prose is not engineering evidence. At completion, confirm at least:

1. Actual changed files match the requested scope.
2. Problems contains no new blocker.
3. AI validated final saved content rather than an intermediate draft.
4. Required Build, Preview, Start, or Debug acceptance is complete.
5. Unverified equipment, safety, permission, and production-write conditions are explicit.

Conversation data and privacy

Understand these behaviors before using AI:

• Complete conversation history is stored on the current device. Legacy records that predate the current conversation index do not automatically appear in the list.
• New AI Command Center conversations, and conversations changed afterward, are archived to the Qixin platform. Current work can continue while offline; archival retries after connectivity returns.
• Retention by the selected model service depends on that service and the organization's policy. Qixin platform conversation archival follows the separate rules below.
• Deleting a local conversation does not delete its platform archive. Platform archives have long-term retention and no automatic expiry.
• Ordinary users, conversation creators, and organization OWNER or ADMIN members cannot read archived content. Only a global platform administrator can audit-preview it, download one original conversation, or perform permanent compliance deletion.
• Platform preview, download, and deletion record the administrator, target conversation, action, and time. Permanent deletion prevents that conversation from being uploaded again.

Never place passwords, API keys, device authorization codes, customer private data you may not upload, or raw production data that must remain on site in a conversation. Before production use, the organization should confirm model-improvement, authorization, access, and deletion rules.

A healthy conversation ending

Ask AI to finish with:

1. Resources actually changed.
2. Diagnostics and runtime checks performed.
3. On-site conditions still unverified.
4. Device, safety, permission, or production-write decisions that remain human-owned.
5. Long-lived constraints that belong in project AI guidance or a reusable workflow.

Next, see Write an acceptable AI engineering task and Use AI Command Center.