continue-session

A command that downloads session files from a Prow CI job and lets you continue the Claude session locally. Prow is a system that runs automated checks for software projects, and CI means continuous integration.

In plain words
What is it for?
Use it with a Prow job URL to find, download, extract, and continue available Claude session archives.
Why use it?
It saves you from starting over when useful work was done inside an automated CI job. It also checks whether the job contains a recoverable session archive.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/openshift-eng/ai-helpers/continue-session
Clone the repo
git clone --depth 1 https://github.com/openshift-eng/ai-helpers
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,447 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.01447
Opus 5 $0.00007 $0.00724
Sonnet 5 $0.00003 $0.00289
Haiku 4.5 $0.00001 $0.00145

Measured 2d ago against content hash 575b1b78751e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

continue-session scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/ci/commands/continue-session.md · 154 lines

How it starts

The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Name

ci:continue-session

Synopsis

/ci:continue-session <prowjob-url>

Description

Downloads Claude session artifacts from a Prow CI job and allows you to continue one of those sessions locally. This is useful when Claude ran as part of a CI job and you want to pick up where it left off.

The command accepts:

  • prowjob-url (required): URL to a Prow job run

Prerequisites

  1. gcloud CLI — for accessing GCS artifacts

    • Check: which gcloud
    • The test-platform-results bucket is publicly accessible (no auth needed)
  2. Python 3 (3.7+)

    • Check: which python3
  3. tar — for extracting archives

Implementation

Step 1: Search for session archives

Load the ci:prow-job-analysis skill and use its artifact search script (prow_job_artifact_search.py) to find files matching **/claude-session*.tar* in the job's artifacts.

Parse the JSON output. If no matches are found (count: 0), tell the user "No Claude session archives found in this job's artifacts." and stop.

Step 2: Download archives to current directory

For each matched archive file, download it from GCS using gcloud storage cp:

gcloud storage cp --no-user-output-enabled <gcs_uri> ./

Step 3: Download payload artifacts

Search for payload artifacts using the ci:prow-job-analysis skill's artifact search script with the pattern **/payload*.yaml, **/payload*.json, and **/payload*.html.

For each matched file, download it to the current directory:

gcloud storage cp --no-user-output-enabled <gcs_uri> ./

These are supplementary artifacts — if none are found, continue without error.

Step 4: Extract archives

For each downloaded archive in the current directory:

# tar auto-detects compression format (.tar, .tar.gz, .tar.zst, .tar.bz2, etc.)
tar xf <filename>

After extraction, the structure contains a projects/ directory. Each session consists of two parts:

  • A JSONL file at projects/<project-path>/<session-uuid>.jsonl (the main conversation log)
  • A directory at projects/<project-path>/<session-uuid>/ (containing subagent data and other session state)

Read the full file on GitHub · 154 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 154 lines · 14 tokens per session scan A 575b1b78751e

Subscribe to this mod's changes

continue-session is a command published in the GitHub repository openshift-eng/ai-helpers (114 stars, last pushed 5d ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,447 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.