Skip to main content

Manage AI sessions

AI Command Center can open full-screen or inside a WorkArea tab. Hiding it or switching views does not automatically stop background work.

Start and continue sessions​

  • Selecting New creates a draft first; the real session is created when the first message is sent.
  • Each app has its own session list, so switching apps does not mix project context.
  • A session can continue in the background when you select another session.
  • An unsent prompt draft is retained for the current app when you switch tabs or temporarily hide AI.
  • Deleting a running session stops that session before removing its history; other sessions are not affected.

Use a separate session for an independent outcome. One session should continue a coherent engineering goal instead of accumulating unrelated tasks indefinitely.

Provide accurate context with @​

Type @ in the prompt box and select a file or bundled Skill from the current app. Common references include:

  • The current .qxpage or .qxcomponent
  • The current .qxgraph
  • queries.json, variables.json, or another configuration file
  • An app-local .cs Script
  • A task-specific Skill such as qxpage, qxgraph, qxquery, or qxscript

Attach only resources related to the current task. More references are not automatically better; stale or unrelated files increase ambiguity.

Queue, run concurrently, and stop​

  • While the current session runs, you can add a follow-up message to its queue.
  • You can switch to another session and start an independent task; the task list shows each session's state.
  • Stop terminates the selected session and clears its messages that have not started.
  • Stopping one session does not stop other background sessions.

Do not modify the same Page, Graph, or configuration file concurrently. If parallel work is necessary, separate the file scopes first, then inspect Git diff and Problems before acceptance.

Model and thinking level​

AI Command Center remembers the most recent available model per app. New sessions use an available model and a thinking level supported by that model. After a Provider or entitlement-mode change, an older model may no longer be selectable.

Choose stronger reasoning for complex cross-module work. Small explanations and focused repairs do not always require the highest level.

App design memory​

After a conversation, AI can write stable app design facts to the auto-managed section of the current workspace's AGENTS.md, such as device semantics, Page conventions, Graph structure, and unresolved questions.

  • Automatic memory updates only the explicitly marked managed section.
  • Manual guidance outside that section is preserved.
  • If the model is unavailable or extraction fails, memory is skipped without affecting the session result.
  • Engineers must still review important facts. Automatic memory is not a device record or safety authority.

Session data collection​

Qixin sign-in by itself does not enable AI-session upload. Theseus synchronizes session snapshots only after the deployment owner or administrator explicitly configures and enables a collection destination and authorization on the device. An unconfigured, disabled, or failed sync does not stop local conversations.

Ask your administrator whether collection is enabled on this device, where the data is sent, why it is collected, and how long it is retained. Whether collection is enabled or not, do not include passwords, API keys, customer-private data, or raw production data that must remain on site.

A healthy session ending​

Before closing a task, ask AI to report:

  1. The resources actually changed.
  2. Diagnostics, Build, or Debug checks that were run.
  3. Site conditions that remain unverified.
  4. Device, safety, permission, or production-write decisions that require a person.
  5. Stable facts worth keeping in app design memory.