Skip to content

release: v0.3.3 — six new CLI commands + speculative-agent recipe#141

Merged
WaylandYang merged 1 commit into
mainfrom
release/v0.3.3
May 21, 2026
Merged

release: v0.3.3 — six new CLI commands + speculative-agent recipe#141
WaylandYang merged 1 commit into
mainfrom
release/v0.3.3

Conversation

@WaylandYang
Copy link
Copy Markdown
Contributor

Summary

Bumps Cargo workspace 0.3.1 → 0.3.3, Python SDK 0.3.2 → 0.3.3, and adds the v0.3.3 CHANGELOG entry. After merge, tag `v0.3.3` to trigger the GitHub Release + PyPI publish chain.

What's in v0.3.3 (against the 0.3.1 release)

  • 6 new CLI commands: `forkd doctor`, `forkd bench`, `forkd from-image`, `forkd ls`, `forkd kill`, `forkd rmi`, plus `forkd snapshot --from-sandbox --diff`. `forkd images` table revamped.
  • 5 framework integration recipes: mcp-agent / crewai-fanout / autogen-branch / openai-swarm / speculative-agent (the headline BRANCH+fanout demo).
  • Phase 2 + 3 pause-window: NVMe + io_uring + pre-emptive background snapshot #118 anomaly probe refinement: thread-level attribution flips the "user-space CPU" story; original Phase 2/3 scope needs revision. See `bench/pause-window/PROBE-multi-branch-anomaly.md`.
  • Quick start rewrite in both READMEs around the new commands.
  • npm publish of `@deeplethe/forkd@0.3.1` (first npm release).

Full notes: CHANGELOG.md § 0.3.3.

What this PR doesn't change

  • TypeScript SDK stays at 0.3.1 — no source changes since the npm publish; bumping just for version-alignment churn would force an unnecessary republish.

Test plan

  • Local build expected to regenerate Cargo.lock (CI uses plain `cargo build`, no `--locked`)
  • Python pyproject.toml + `version` aligned at 0.3.3
  • Post-merge: tag `v0.3.3` → release.yml builds + creates GH release → publish-pypi.yml fires (may need workflow_dispatch fallback per v0.3.2 precedent)
  • Verify `forkd==0.3.3` on PyPI

🤖 Generated with Claude Code

Bumps:
- Cargo workspace 0.3.1 → 0.3.3
- forkd Python SDK 0.3.2 → 0.3.3 (alignment; no new Python code)

What ships in v0.3.3 (since 0.3.1 tag, six weeks of work but mostly
the last 48 hours of dev-experience polish):

CLI cluster:
- forkd doctor    — 10 host-readiness checks + fix hints
- forkd bench     — screenshot-friendly latency probe
- forkd from-image <image> --tag <X> — Docker → snapshot in one verb
- forkd ls        — list live sandboxes (table)
- forkd kill <ID>... / --all / --tag — kill sandboxes
- forkd rmi <tag>... — delete snapshot tags (docker-style)
- forkd snapshot --from-sandbox --diff — v0.3 Diff path on CLI
- forkd images output revamped (MEMORY column, age, totals, sort)

Five framework integration recipes:
- mcp-agent, crewai-fanout, autogen-branch, openai-swarm
- speculative-agent (the headline BRANCH+fanout demo — judge picks
  fastest of N strategies, 2595× speedup vs slowest in the example)

#118 anomaly investigation:
- Probe refined to thread-level. FC is off-CPU ~94% of slow BRANCH;
  futex contention + ext4 journal IO + user CPU on snapshot worker.
  Original Phase 2/3 scope of #118 needs revision.

Quick start in README + README-zh rewritten around forkd doctor +
forkd from-image + forkd bench (the modern user path).

Full notes in CHANGELOG.md.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@WaylandYang WaylandYang merged commit ba81986 into main May 21, 2026
2 checks passed
@WaylandYang WaylandYang deleted the release/v0.3.3 branch May 21, 2026 07:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant