Adds Import Codex sessions to the workspace and Explorer + menus. Find and reopen local Codex conversations, including archived history. The interface follows the language selected in Paseo.
Requires Paseo 0.15.4 or later, Node.js 22.19 or later, and Codex CLI 0.167.0 or later on the daemon machine. Tested on Linux. The panel uses React Native and supports desktop and compact clients.
Enable plugins in Settings → Plugins, then install on the host that stores your Codex history:
paseo plugin install github:tenlee2012/paseo-codex-importerYou can also enter github:tenlee2012/paseo-codex-importer in Settings → Plugins. Installation obtains the pinned runtime dependencies from the public npm registry. Paseo plugins are trusted code with the daemon user's file and process access.
For an existing GitHub installation, review and apply the update with:
paseo plugin update codex-importerTo install this release directly, add --ref v0.2.2 to the install command. To update an existing installation to this release without a prompt, use paseo plugin update codex-importer --ref v0.2.2.
- Open the workspace where you want to continue the conversation.
- Select + → Import Codex sessions in the workspace or Explorer panel. On mobile, use + beside Files / Changes. The action is also available in the Command Center.
- Current workspace is selected by default. Switch to All paths to include history from other directories on this host. Each row then shows its original directory; the import destination stays visible above the filters.
- Search by title or choose All, Archived, or Unarchived. The path and archive filters are independent. Changing paths starts pagination for that scope while keeping the search and archive filter.
- Click Import. Every successful import belongs to the workspace that opened this panel and uses its directory for subsequent work.
For the same directory, the importer restores the original native Codex thread. Its thread ID stays unchanged. Paseo reuses a matching archived agent with the same provider and directory, even when the destination workspace differs. Directory aliases are compared using filesystem real paths.
For a different directory, the importer uses Codex's native fork operation to copy stored history into a new thread ID in the current workspace. It preserves a custom conversation title when one exists. The source conversation and its previous Paseo workspace are retained. Codex requires an archived source to be temporarily unarchived for a fork; the importer re-archives it before importing the copy. It does not copy project files. A copied conversation subsequently closed in the current directory can be restored there as the same session.
The list includes non-subagent CLI, editor, app-server, and exec history from the selected host's configured Codex home. It follows Codex pagination and orders conversations by last update. Title search follows Codex's search behavior, including case sensitivity. All paths changes the directory filter, not the selected host or Codex configuration.
Conversations already owned by active Paseo agents, including configured providers extending Codex, are excluded across workspaces. When a copy is already open in the current workspace, its source is also excluded there to prevent duplicate imports. That source remains available in other workspaces. Importing from this panel uses the built-in codex provider and its current configuration.
Opening or searching the panel does not change archive state. Importing affects only the selected history. Closing an agent tab still follows Paseo's archive behavior; you can find it again with this plugin.
If preparation succeeds but Paseo import fails, restored or copied history may remain in Codex. Refresh Current workspace → Unarchived to find the prepared copy before trying the source again. If restoring the source's archive state fails, or the plugin stops during a copy, check the original conversation's archive state before retrying. A reported success means the returned agent's workspace and working directory both match the destination.
The plugin follows Paseo → Settings → Language in each connected client. With System, it uses Paseo's resolved system language. Changing the app language updates menus, panel titles, buttons, accessibility labels, status messages, and errors immediately, preserving search drafts, filters, loaded results, and import feedback.
Supports English (en), Arabic (ar), Spanish (es), French (fr), Japanese (ja), Korean (ko), Brazilian Portuguese (pt-BR), Russian (ru), and Simplified Chinese (zh-CN). Dates, numbers, and plural forms use the client locale. Other plugin locales fall back to English. Each client can display a different language independently.
Session titles, workspace names, paths, and provider names keep their original values. Translation resources ship with the plugin and require no translation service or upload of history. Updating from v0.1.0 replaces the fixed Chinese interface; reload the client if it still displays an older cached bundle.
The backend reads the selected host's Codex command and environment from Paseo configuration and calls the local codex app-server APIs. It reads Paseo's local daemon identity and local connection credential to use the official Node import client; these values stay in backend memory. It never returns credentials, raw process stderr, or provider error messages to the client or plugin logs.
Conversation titles, directory names, timestamps, and IDs travel to your authorized clients through your existing Paseo connection. The plugin has no telemetry, public data upload, or external history service. Listing and importing do not submit a model turn. Continuing the conversation afterward uses your normal Codex/provider settings.
All repository examples, tests, and screenshots use synthetic data. Real histories, credentials, local configurations, debug artifacts, and databases are excluded from publication. See PRIVACY.md for the release checks.
npm ci --legacy-peer-deps --ignore-scripts
npm run typecheck
npm run lint
npm run format:check
npm test -- tests/translations.test.ts
npm test -- tests/codex.integration.test.ts tests/catalog.integration.test.ts tests/imports.integration.test.ts
npm run test:browser
npm run check:privacyInstall the Paseo and Codex CLIs before running integration checks. Browser checks require Playwright Chromium (npx playwright install chromium) or PLAYWRIGHT_CHROMIUM_EXECUTABLE pointing to an existing Chromium executable.
Tests create isolated temporary Codex homes and a separate Paseo daemon on an automatically assigned loopback port. They use synthetic rollout files, start no model turns, and stop only their own temporary daemon. Translation tests use Paseo's real translation engine. Browser checks exercise the real component and plugin RPCs, all nine live languages, independent client languages, locale dates, preserved query state, path-scoped pagination, and same-directory restoration versus cross-directory copying. Temporary browser bundles and diagnostics go to the ignored .artifacts/ directory.
Install your checkout with paseo plugin install /absolute/path/to/checkout. After source changes, run paseo plugin reload codex-importer; a daemon restart is unnecessary.
MIT licensed. This is an independent community plugin.
