Continue Command

The smippo continue command resumes an interrupted capture. If your capture was stopped mid-way (network issues, timeout, Ctrl+C), you can pick up where you left off.

Basic Usage

smippo continue [options]

Resume Default Directory

Continue a capture in the default ./site directory:

smippo continue

Resume Custom Directory

Continue a capture from a specific directory:

smippo continue -o ./my-mirror
smippo continue --output ~/archives/docs

How It Works

When Smippo captures a site, it creates a .smippo/manifest.json file that tracks:

Original URL
Capture options used
Pages already captured
Pages queued but not yet captured
Assets saved

The continue command reads this manifest and resumes from where the capture stopped.

.smippo/
├── manifest.json    # Capture state & progress
├── cache.json       # ETags and last-modified dates
└── network.har      # HTTP archive

When to Use Continue

Network Interruption

If your network disconnected during a large capture:

# Original capture (interrupted)
smippo https://docs.example.com --depth 5
# ^C or network failure

# Resume
smippo continue

Timeout

If the capture hit a timeout but there are still pages to capture:

smippo continue

Intentional Pause

If you need to pause a large capture and continue later:

# Start capture
smippo https://large-site.com --depth 10

# Press Ctrl+C when you need to pause

# Later, resume
smippo continue

What Gets Resumed

Queued pages — Pages discovered but not yet captured
Partial links — Links from pages that were captured
Options — All original capture options are preserved

What Doesn't Resume

In-progress pages — If a page was being captured when interrupted, it will be re-captured
Modified options — The original options are used; you can't change depth, scope, etc.

To change capture options, use smippo update instead, which performs a fresh crawl with new options while skipping already-captured pages.

Verbose Output

See detailed progress when resuming:

smippo continue --verbose

This shows:

Pages being skipped (already captured)
New pages being captured
Queue status

Error Handling

No Manifest Found

If there's no previous capture to continue:

✗ Error: No capture found in the specified directory. Start a new capture first.

Corrupted Manifest

If the manifest is corrupted, start a fresh capture or manually fix the JSON.

Practical Example

Large documentation site capture:

# Day 1: Start the capture
smippo https://docs.framework.com --depth 10 --workers 4

# Captured 500 pages, then network issue...

# Day 2: Continue
smippo continue -o ./site

# Continues from page 501, skips already-captured pages

All Options

Option	Description	Default
`-o, --output <dir>`	Output directory with existing capture	`./site`
`-v, --verbose`	Verbose output	`false`

Update Command — Re-crawl with new options
Capture Command — Start a fresh capture