remote-collection
FeaturedConfigure and troubleshoot CCAM Remote Data Sources that collect Claude Code and Codex history over SSH. Use when adding, editing, testing, syncing, or removing a remote machine, verifying provider paths, or deciding whether to retain or purge imported sessions.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- hoangsonww
- Repository
- hoangsonww/Claude-Code-Agent-Monitor
- Created
- 6 months ago
- Last Updated
- 2 days ago
- Language
- TypeScript
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
codex-remote-control
Inspect and address Codex CLI sessions from inside Claude Code. Use when the user asks what Codex is doing, whether it is stuck or idle, how far along it is, what its rate limits are, which Codex sessions exist or are running, what a session was asked to do, what model or reasoning effort it is using, or asks to tell/instruct/message a Codex session. Sessions can be found by uuid, by working directory, or by words in their opening prompt. Also use for 'check on codex', 'is codex still running', 'codex status', 'list codex sessions', 'what is the codex session in <dir> doing'.
history-portability
Import Claude Code or Codex history and move complete CCAM datasets between machines. Use when rescanning provider history, importing a copied directory, uploading JSONL or archives, exporting a backup, restoring it idempotently, or verifying that tokens, workflows, runs, rules, and pricing survived.
ccbox
Inspect and summarize local Codex/Claude session logs using the ccbox CLI (projects, sessions, history). Use when asked to list discovered projects, find sessions for the current repo/folder, print a session timeline, or produce an evidence-based “what happened��� report from a session .jsonl log under CODEX_SESSIONS_DIR.