Skip to content

Quickstart

Four steps. Each is one command. Skip any you don’t need.

Terminal window
git clone https://github.com/cybersader/portaconv
cd portaconv
cargo install --path .

pconv now lives on your $PATH. See Installation if you want more detail (requirements, platform notes).

Terminal window
pconv list
# Often more useful — only this workspace, last 2 days
pconv list --workspace-toml auto --since 2d
# Or just grab the latest and skip the id-copying step entirely:
pconv dump --latest --workspace-toml auto | clip.exe # WSL

The one-liner at the end is the “I just want yesterday’s context back” shortcut — no need to eyeball a list and copy a UUID. Read on for the step-by-step view.

Output looks like this (table format, newest first):

session-id msgs updated cwd title
----------------------------------------------------------------------------------------------------------------------------------
2d23322b-40ea-41a3-99ed-9c14569a44b8 453 2026-04-20 13:51 …Workspaces/portaconv porting docs from portagenty
97d7b58b-09f5-41ea-a59f-a12f230083b0 8152 2026-04-20 13:25 …/mcp-workflow-and-tech-stack trying to develop a good workflow…
b1f7edc9-9a75-4c21-9067-4de665cb3d7c 7461 2026-04-20 12:37 …Workspaces/cyberbaser need to really initialize this…
75 session(s)

Columns: session-id · msgs · updated · cwd · title. cwd is truncated with a leading — projects are usually more recognizable by their tail segments than their home-dir prefix.

Pick the id you want. It’s the first column. (Tip: pconv list --workspace-toml auto scopes to the current portagenty workspace if you’re in one — much shorter list.)

Terminal window
pconv dump 2d23322b-40ea-41a3-99ed-9c14569a44b8

You get markdown like this on stdout:

# porting docs from portagenty
- session: `2d23322b-40ea-41a3-99ed-9c14569a44b8`
- cwd: `/mnt/c/Users/.../portaconv`
- started: 2026-04-20 00:13 UTC
- git branch: `main`
## User
let me plan the docs restructure before I touch anything
## Assistant
Sounds good. Let me see what's there first.
**tool call:** `Read`
\`\`\`json
{
"file_path": "/path/to/docs/src/content/docs/index.mdx"
}
\`\`\`

That’s what an agent wants pasted back as context.

Terminal window
# WSL → Windows clipboard
pconv dump <id> | clip.exe
# macOS
pconv dump <id> | pbcopy
# Linux with Wayland
pconv dump <id> | wl-copy
# Save to the repo
pconv dump <id> > docs/agent-context/2026-04-20-redesign.md

Paste into Claude Code (new chat), claude.ai, opencode, or anywhere you want to continue.

If the session was authored on the other OS, translate paths on the way out:

Terminal window
# WSL-authored session → heading into Windows
pconv dump <id> --rewrite wsl-to-win | clip.exe
# Windows-authored session → heading into WSL
pconv dump <id> --rewrite win-to-wsl
# Pasting somewhere with no filesystem at all (claude.ai, API)
pconv dump <id> --rewrite strip

See path rewriting on the homepage for concrete before/after pairs.

Long sessions don’t always fit — or shouldn’t — in a fresh agent’s context. --tail N keeps only the most-recent N messages:

Terminal window
pconv dump <id> --tail 50 # last 50 msgs only
pconv dump --latest --workspace-toml auto --tail 30 # latest in workspace, last 30

The output is self-documenting about what got dropped:

  • Markdown gets a header line: - truncated: last N of T messages (D earlier dropped)
  • JSON gets extensions.truncated = { tail, original_message_count, dropped } so agents can detect the slice programmatically

Stacks cleanly with the rewrite and thinking/results flags.

Instead of shelling out, let an MCP-capable agent call portaconv directly. Add this to your agent’s MCP config (e.g. ~/.claude/mcp.json):

{
"mcpServers": {
"portaconv": {
"command": "pconv",
"args": ["mcp", "serve"]
}
}
}

The agent now has two tools: list_conversations and get_conversation. It can pull in prior context on its own, no copy-paste needed. Full details on the agents + portagenty page.

  • Commands reference — every flag, every output format.
  • Concepts — how portaconv thinks about your conversations (subagent filter, multi-session files, what survives the paste).
  • Agent wiring + usage patterns — four real-world recovery patterns: post-/compact, cross-tool handoff, committed artifacts, agent-as-curator.