SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillslov-open-codex-session

lov-open-codex-session

General & other

View repository

Updated 10-16 00:01

About this skill

lov-open-codex-session — Open a specified Codex task

Hand the stable Codex sessionId / threadId to the host's navigation capability so the current Codex main window switches to the exact task. The Skill is only responsible for locating and opening; it does not modify task content, archive status, or Git status.

Triggers

Activate when

  • "Open this session", "open the WeRead submission session just found", "go directly to this Codex task".
  • The user provides a Codex thread UUID or codex://threads/<uuid>and asks to open, jump to, or navigate.
  • “Open this Codex session”, “navigate to that Codex thread”, “show the task we just found”.

Do not activate when

  • The user wants to find sessions that discussed a certain topic in the past, but no unique candidate has been obtained yet — first use lov-search-chat to search and read back the original text.
  • The user wants to generate a public share link — use lov-share-session。
  • The user wants to count the tokens of a single task — use lov-codex-thread-usage。
  • The user wants to create, duplicate, or fork a task — use the host's corresponding create or fork capability.

User Profile (cross-session)

skill.yaml declares user-profile/v1. At the start of each run, read the shared user, brand, workspace, preferences, and skills.lov-open-codex-session namespaces. The thread ID in the current request always takes priority, and the thread ID, title, and transcript content are never written to the persistent Profile.

Only when the user has directly stated an open preference that needs to persist across sessions, write via scripts/profile_store.py record --confirm to records.*, and report the save path. For the full contract, see references/user-profile.md。

Skill Group Composition

Read before running references/skill-composition.md。lov-search-chat can deliver a stable sessionId, but retrieval is not a hidden dependency of this Skill; when a UUID or deeplink is already given, navigate directly.

Workflow (MANDATORY)

You MUST follow these steps in order.

Step 0: Resolve runtime context

  1. Read skill.yaml, the shared Profile, and references/skill-composition.md。
  2. confirm that the current host provides navigate_to_codex_page or a semantically equivalent Codex task navigation tool.
  3. If the host has no task navigation capability, clearly report the missing capability; do not use open, a browser deeplink, AppleScript, or Computer Use to fake equivalent success.

Portable command to read the Profile:

python3 "$SKILL_DIR/scripts/profile_store.py" read \
  --skill-id lov-open-codex-session --pretty

Step 1: Resolve exactly one target

Obtain the target in the following priority order:

  1. The thread UUID in the current request.
  2. The codex://threads/<uuid>in the current request; extract only the UUID part.
  3. The unique sessionId / threadId。
  4. When there is only a description and no ID, call lov-search-chat or the host task list to locate candidates; a search hit must have its title and original text read back, and must not be judged by snippet.

Accept standard UUIDs; reject empty values, truncated values, paths, arbitrary URLs, and multiple undisambiguated candidates. Ataru's Codex sessionId can be used directly as a Codex threadId。

Step 2: Open the target

Call the host task navigation capability:

navigate_to_codex_page(threadId=sessionId)

Do not unarchive first, do not create a new task, and do not send a message to the target task. Opening an archived task is not the same as changing its archive status.

Step 3: Verify and report

  1. Must check that navigated in the tool result is true。
  2. If the title is known, answer "Opened 《title》"; otherwise answer "Opened the target Codex task", with a short ID for verification.
  3. When the tool fails, keep the exact error and target ID, and do not report "opened".
  4. If the user also requests continuing, sending a message, unarchiving, or renaming, these are new external actions; hand them to the corresponding host capability.

Validation

  • Activation phrase: "Open the Codex session that was just found."
  • Deeplink activation phrase: "Open codex://threads/00000000-0000-0000-0000-000000000000. ”
  • Non-trigger phrase: "Generate a public share link for this session."
  • Real acceptance is based on what the host returns as navigated: true ; parsing out only the UUID does not count as complete.

Dependencies

  • Task navigation capability for the Codex desktop host.
  • Python 3.8+, used only for reading and persisting the shared Profile.
  • lov-search-chat is an optional upstream when there is no explicit ID, not a required dependency.