external sessions: an imported task does not record where it came from

Importing an external conversation is a one-shot conversion (packages/storage/src/external-sessions.ts). createImportedSession takes a CreateSessionInput plus messages; nothing on the resulting Session records the adapterId + sourceSessionId it came from. (session.ts's sourceSessionId is revision lineage, a different thing.)

So the import page cannot know what it has already done. That single gap shows up as four separate-looking problems:

No 已导入 marking is possible. A row cannot say "you already imported this one", so 「再次导入同一个对话会创建一个独立的任务」 can only ever be an unconditional standing disclaimer, never per-row information. refactor(desktop): let the import page name the conversation it lost track of #3075 tried to move it next to the action and had to revert.
An unconfirmed import is only remembered until the page closes. uncertainIds is page-local state, so the lock disappears on remount — and the banner can only say "go look in the task list yourself", because the page cannot look for the user.
An in-flight import loses its label on remount. Navigating away and back resets importingId. The import itself is safe — the Host coalesces concurrent duplicates — but the button stops saying what is happening. Raised in refactor(desktop): rebuild the task rail on one shape and one vocabulary #3033's review thread and never filed until now.
Paging can only offer a cursor. Without a total there is no "N remaining", so an append has nothing informative to show. refactor(desktop): let the import page name the conversation it lost track of #3075 tried skeleton placeholder rows and reverted them.

Shape of a fix

Persist the external origin on the imported session, and let the Host answer "what is the import state of this external session" (never imported / imported N times, with ids / import in flight). Then:

each row has a real three-state, and the duplicate consequence becomes a per-row fact
an unconfirmed import stays locked across remounts, and the banner can offer the task instead of asking the user to search
the in-flight label survives remount, and survives a second window or the CLI, which page-level state never could
a count alongside the cursor makes "还剩 12 个" possible

Scope

Touches storage schema, the external-session protocol, HostExternalSessionCoordinator and the Desktop page. Per AGENTS.md this is a public contract change: it needs independent human review and cannot take the self-merge fast path. Worth deciding whether the import page justifies it before anyone starts.

Refs #2984, #3033, #3075

refactor(desktop): let the import page name the conversation it lost …

I’m interested in taking this issue once the direction is confirmed.

I reviewed the current import path and would propose the following approach.

Durable provenance

Persist an immutable external origin on Sessions created through the dedicated import path:

externalOrigin?: {
  adapterId: string;
  sourceSessionId: string;
};

The origin should be persisted atomically with the imported Session and its messages.

I would keep this out of the general CreateSessionInput, so ordinary Session callers cannot manufacture external provenance.

The origin should belong only to the Session directly created by the import and should not propagate to branches, revisions, subagents, or other derived Sessions.

Storage could then expose an indexed lookup or projection keyed by (adapterId, sourceSessionId). This should not be unique, since repeated imports remain valid.

Host projection

Rather than introducing a separate per-row query, I suggest including import information in external-session.catalog.query, roughly:

importState: {
  importedCount: number;
  importedSessionIds: string[]; // potentially bounded, newest first
  isImporting: boolean;
};

The ID list could be bounded to preserve the external-session protocol result-size limit, while importedCount would still report the complete number of recorded imports.

I prefer orthogonal fields over a strict never-imported | imported | importing union, because a source conversation may already have one or more imported copies while another import is currently in flight.

The Host would derive this state from:

durable published Sessions found through the origin lookup; and
the existing #importsInFlight map for live operations.

This would make import state observable across page remounts, Desktop windows, and other clients instead of relying on page-local state.

Desktop and legacy behavior

The Desktop page could then stop treating importingId and uncertainIds as authoritative and refetch Host state after a commit_outcome_unknown result.

Existing imports cannot be reliably backfilled because their external source identity was never persisted. An empty lookup should therefore mean “no recorded import” rather than implying that the source was never imported historically.

Pagination

The totalCount / “N remaining” problem appears independent from provenance. Since the Host already materializes the adapter result before paging, I think this could be handled separately, ideally in a follow-up PR unless the intended scope of this issue is explicitly to address all four UI problems together.

If this overall direction and the pagination split look reasonable, I’d be happy to take this issue. Please assign it to me, and I’ll coordinate the Desktop-side changes with #3075 to avoid overlapping work.

Assigned!

Navigation Menu

Repository navigation

external sessions: an imported task does not record where it came from #3081

Shape of a fix

Scope

Durable provenance

Host projection

Desktop and legacy behavior

Pagination

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

external sessions: an imported task does not record where it came from #3081

Description

Shape of a fix

Scope

Activity

Sun-GLiang commented on Aug 16, 2026

Durable provenance

Host projection

Desktop and legacy behavior

Pagination

Astro-Han commented on Aug 16, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions