You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Living tracker for the roadmap defined in planning/milestones.yaml. Each milestone here links to its detailed task entries in planning/tasks.yaml. Source of truth lives in those files — this issue is the at-a-glance view.
Last refresh: v0.6.5 (2026-05-11).
Status legend
✅ done (in main)
🟡 in-progress / partial
🔵 planned
⚫ deferred to v1.5
🅿️ parking lot — design RFC needed
✅ Completed milestones (v0.1 → v0.6.5)
Core engine + UI
M0 Scaffold + CI + planning docs
M1 Vertical slice (HTTP engine + minimal UI)
M2 Collections & file format (.sman primary, .req.yaml legacy)
M2.5 UI polish pass (Postman light)
M2.6 Tabs + curl import (now on @scrape-do/curl-parser since v0.6.4)
electron-builder + tag-driven release workflow → v0.1.0 published
Cross-platform shortcut layer (mod → ⌘ on macOS, Ctrl elsewhere)
[feat] grpc support #41 gRPC support — large effort, niche for the scraping use case. Revisit when WebSocket + SSE adoption matures.
Request chaining via variable capture (no script sandbox)
Response diff (between two runs or two history entries)
Quick-look eye icon for env variables (peek resolved values)
Comments on .req.yaml / .sman files
Snippet library for common Scrape.do patterns
GraphQL dedicated body editor (basic JSON body editor handles the common case today)
🅿️ Parking lot — design RFC needed
Items here stay open until concrete user demand surfaces a use case that genuinely doesn't fit as a built-in. Each is too high-blast-radius to design speculatively.
Updated by hand on every Scrapeman release. The feedback_landing_sync memory rule also forces an audit of scrapeman-landing at the same time so the docs site doesn't drift.
A bot to autogenerate this from CHANGELOG.md + closed issues is on the M10 polish list.
Living tracker for the roadmap defined in
planning/milestones.yaml. Each milestone here links to its detailed task entries inplanning/tasks.yaml. Source of truth lives in those files — this issue is the at-a-glance view.Last refresh: v0.6.5 (2026-05-11).
Status legend
✅ Completed milestones (v0.1 → v0.6.5)
Core engine + UI
@scrape-do/curl-parsersince v0.6.4)mod→ ⌘ on macOS, Ctrl elsewhere)Variables + auth
{{var}}HighlightedInput{{random}},{{uuid}},{{timestamp}},{{timestampSec}},{{isoDate}},{{randomInt}})Request surface
Scraping-first
Response viewer + Dev tools
Editors + ergonomics
⌘LURL bar focus → [feat] ⌘L / Ctrl+L to focus URL bar (Chrome-style) #1⌘Dduplicate tab → [feat] Duplicate tab (⌘D) #8⌘Kcommand palette → [feat] Linear-style command palette (⌘K) #9⌘1..9switch tab by index⌘Shift+Treopen closed tab⌘RInsomnia-style parallel send (v0.6.2)⌘Ascope leak (HighlightedInput + Code panel)⌘Fin response body{{var}}in URL host segmentLoad + collection
{{random}}/{{timestamp}}regen verifiedStreaming
Scripting
bru+req+resAPI, captured console,test()/expect().toBe())Workspaces + git
Import / export
Body editor
{{var}}decoration + autocomplete + JSON lint gutter + lenient JSON beautify with auto-fix (JSON5 + missing-comma repair)<base href>+ relaxed CSPReleases shipped
🟡 In-progress / partial
🔵 Planned
postman-code-generatorsintegration (20+ langs).brufolder importer⚫ Deferred to v1.5
.req.yaml/.smanfilesItems here stay open until concrete user demand surfaces a use case that genuinely doesn't fit as a built-in. Each is too high-blast-radius to design speculatively.
Source files
planning/milestones.yaml— milestone metadataplanning/tasks.yaml— granular task breakdownplanning/postman-parity.md— feature checklist vs Postmanplanning/session-state.md— current dev statusplanning/architecture.md— D1–D8 decisionsCHANGELOG.md— every shipped versionHow this issue stays in sync
Updated by hand on every Scrapeman release. The
feedback_landing_syncmemory rule also forces an audit of scrapeman-landing at the same time so the docs site doesn't drift.A bot to autogenerate this from CHANGELOG.md + closed issues is on the M10 polish list.