Skip to main content
skill CX Codex

remote-collection — Claude Code skill: pull history over SSH

A skill that walks the agent through CCAM remote data sources: connect machines over SSH and pull Claude and Codex history. Useful when sessions live beyond your laptop.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill remote-collection -a claude-code
Open on GitHub

What remote-collection does

The skill covers the whole lifecycle of a CCAM remote source: listing, adding, testing, syncing, editing and removing. Start with ccam remote-sources to see what is already configured. Host validation runs through your existing SSH setup, since CCAM keeps no passwords and no private keys.

Set remote_home and remote_codex_home only when those paths differ from the provider defaults. Test a source before syncing it: ccam remote-sources test <id>. Then ccam remote-sources sync [id] pulls one source or every source at once, and edits go through ccam remote-sources update <id> --file patch.json --yes.

Removing a source keeps imported sessions unless you ask otherwise. Purging needs the extra flag: ccam remote-sources rm <id> --purge --confirm PURGE_REMOTE_SOURCE_DATA. Miss the confirmation token and nothing gets wiped, so a stray command will not take your history with it. The skill also insists you say out loud whether imported data survives the removal.

What it helps with

  • attach a remote machine and pull its Claude history
  • test a source before syncing so you do not import an empty set
  • fix a non-default Codex path on a server
  • sync every configured source in one go
  • drop a source while keeping the sessions already imported

Example prompts for the agent

  • List the current CCAM remote sources
  • Add a source for a machine where Codex history sits in a different directory
  • Remove a source and tell me whether imported sessions are kept

How to install remote-collection

1Skills CLI (Vercel)

npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill remote-collection -a claude-code

2Manually: put the files in place

~/.claude/skills/remote-collection/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/remote-collection/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about remote-collection

How do I install remote-collection in Claude Code?

Run npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill remote-collection -a claude-code. The skill file lands at ~/.claude/skills/remote-collection/SKILL.md.

What does remote-collection do?

It guides the agent through every step of managing CCAM remote sources: listing, adding, testing, syncing, editing and removing. It also makes sure you state whether imported sessions are kept before a removal goes ahead.

Does it need passwords or SSH keys stored somewhere?

No. The host check uses the SSH configuration you already have, and CCAM stores neither passwords nor private keys.

Source text

SKILL.md · MIT
---
name: remote-collection
description: >
  Configure 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.
---

# Remote Collection

1. List current sources with `ccam remote-sources`.
2. Validate the host through the user's existing SSH configuration. CCAM stores
   no passwords or private keys.
3. Add a source with `remote_home` and `remote_codex_home` only when they differ
   from the provider defaults.
4. Test before syncing: `ccam remote-sources test <id>`.
5. Sync one source or all sources with `ccam remote-sources sync [id]`.
6. Use `ccam remote-sources update <id> --file patch.json --yes` for edits.
7. Removal retains imported sessions by default. Purging them requires:

```bash
ccam remote-sources rm <id> --purge \
  --confirm PURGE_REMOTE_SOURCE_DATA
```

Always state whether imported data will be kept or deleted before removal.

© hoangsonww · MIT · hoangsonww/Claude-Code-Agent-Monitor

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set20

api-error-report Turns Agent Monitor data into a report on APIError events: how many, in which sessions and models, and what likely caused them. CX Codex +1 ★ 1,121repo stars time-of-day Sorts sessions and events into hour-of-day and day-of-week bins, then marks peak and low-output windows. Useful when you plan a work schedule. CX Codex +1 ★ 1,121repo stars daily-standup Turns your recent Claude sessions into a standup report: work done per project, errors hit, what it cost. CX Codex +1 ★ 1,121repo stars history-portability Pulls in Claude or Claude history and shifts whole CCAM datasets between machines. Useful when you switch laptops or need a restore. CX Codex +1 ★ 1,121repo stars regression-watch Compares an older baseline window of session history with a recent one and reports which metrics got worse: errors, cache, compactions, cost per session. CX Codex +1 ★ 1,121repo stars benchmark The benchmark skill takes one session or a few recent ones and compares them with the rolling average from Agent Monitor data: cost, tokens, tool count and workflow complexity. Each metric comes back as a percentile of the population. CX Codex +1 ★ 1,121repo stars session-debug Pulls a single Claude session out of Agent Monitor and reports its event chain, subagent tree, token spend and failures. CX Codex +1 ★ 1,121repo stars event-trace Turns one Claude session into an ordered timeline of its events, flagging gaps, failures and tool calls that never finished. CX Codex +1 ★ 1,121repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor