remote-host-context

Collects read-only Codex session evidence across local and SSH remote hosts.

Updated May 18, 2026
One-click install
npx skills add https://github.com/Joey-Tools/codex-private-workflows --skill remote-host-context-joey-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remote-host-context
Source: https://github.com/Joey-Tools/codex-private-workflows/tree/main/personal_codex/skills/remote-host-context
Command: npx skills add https://github.com/Joey-Tools/codex-private-workflows --skill remote-host-context-joey-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Work reports, session summaries, and context recovery often miss activity that happened on remote machines. This Skill standardizes a read-only SSH preflight and bounded evidence collection across Joey's default hosts (local machine, BL-mac-mini-m4-hoteng, hoteng-srv-01, and codex-hoteng-srv-01) so cross-host Codex work is never silently dropped. ## Core Features & Use Cases - Bounded Remote Preflight: Checks each default host for reachability, user/home identity, ~/.codex presence, and tool availability before any deeper reads, reporting the exact failure gate. - Safe Rollout Access: Provides session-meta, rollout-stat, rollout-summary, chunked-rollout-summary, fetch-rollout, fetch-rollout-chunk, and terminal-tail commands with strict byte caps, identity pinning, and symlink-safe descriptor-based file access. - Verified Full Reconstruction: Validates complete chunk plans against a 128 MiB budget, verifies SHA-256 and final stat, then delegates the exact JSONL record stream to codex-session-mining. - Use Case: When writing an Apple Notes work report, run the default preflight across all four hosts, locate relevant rollouts by creation date with session-meta, and merge remote evidence before concluding any task is missing from the report. ## Quick Start Run the remote-host-context preflight across the local machine and all three default SSH hosts to check which Codex evidence roots are reachable before summarizing recent work.

Frequently Asked Questions about remote-host-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check Codex session history on remote hosts over SSH?

Run the remote_codex_probe.py preflight command with a repeatable --host flag for each target host. It performs a read-only check of reachability, user and home identity, ~/.codex presence, and tool availability before any deeper reads.

How do I recover a Codex thread from a codex://threads URL?

Derive the thread's creation date first, then run session-meta against that creation-date directory and filter by the exact session id. Avoid read_thread unless the service enforces item-type filtering, item-count limits, and a 32 KiB whole-response byte cap.

What is the file size limit for copying a remote rollout file?

Direct whole-file fetch-rollout copies are capped at 16 MiB. Larger rollouts use chunked-rollout-summary with fetch-rollout-chunk under a validated plan capped at 128 MiB, beyond which explicit per-rollout authorization is required.

Why does session-meta report a truncated or coverage-gap error?

session-meta fails closed when its byte cap cuts through a record, when the 501-candidate safety budget is exhausted, or when an active rollout changes during scanning. Narrow the date or host scope and retry rather than treating the gap as proof of missing metadata.

Can this Skill modify files on remote hosts?

No. All remote operations are read-only by policy; remote hosts contribute evidence only. Writes stay local under a task-scoped .codex-tmp/remote-host-context directory or /tmp unless the user explicitly authorizes remote modification.