Skip to content

[Feature Request] Import builtin Pi sessions through local history sync #966

Description

@Astro-Han

Affected area

Agent runtime / ACP

Problem or workflow pressure

Local project history sync ("Conversation sync") cannot import builtin Pi sessions. Selecting Pi fails immediately with:

builtin:pi ACP agent does not advertise sessionCapabilities.list

The history importer lists sessions with ACP session/list and imports one with session/load, but the managed Pi adapter (packages/acp-extension-pi) only implements session/resume. Users who work in Pi's own terminal UI, or who created Pi chats before, cannot bring those sessions into Lody.

Desired outcome

Pi sessions for a project appear in Conversation sync and can be imported with their user messages, assistant text/thinking, tool calls and todo checklists. Continuing an imported session resumes the same native Pi session file. Ordinary Pi chat resume keeps its current behavior (no full-history replay).

Proposed solution

  • Adapter (feat: list and load native Pi sessions over ACP acp-extension-pi#4): session/list reads Pi's native session files read-only through Pi's own SessionManager; session/load switches like resume, then replays the current branch from get_entries with Pi's own tool call ids.
  • Host: prefer session/resume over session/load for builtin Pi, as already done for Kimi, so advertising loadSession does not change ordinary resume.
  • Maintainers publish a new managed Pi runtime artifact from the adapter revision.

Alternatives or workarounds

Codex uses the Lody extension _lody/session/history/read instead of session/load, but the importer gates it to builtin Codex; standard ACP load needs no provider branch in the importer.

Trade-offs or non-goals

Images, compaction summaries and abandoned branches are not replayed. Legacy pi-acp session ids remain non-resumable.

Additional context

No response

Before submitting

  • I searched the existing issues and did not find a duplicate request.
  • This request concerns an open-source component in this repository, not a hosted service, Web or mobile app, account, or billing issue.
  • I removed credentials, private source, conversations, prompts, personal data, and other sensitive information.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions