Repository navigation
Scope 1.3.0 — pause, edit, continue
Scope 1.3.0 — pause an endpoint, edit the real message
Traffic rules can now pause a matching request, response or both for manual
editing. Match a host/path, choose Pause & edit, then send traffic through
Scope. The editor contains the message that actually arrived. Change request
method/URL/headers/body or response status/headers/body, then Send with changes,
Continue unchanged, or abort the message. Other endpoints keep moving.
The paused-message banner is available from every workspace, including Traffic
rules. Editing remains available during unrelated UI work. Original messages
and the rules actually applied remain recorded in the session.
The proxy port field also keeps your typed value while status polling runs,
validates it before starting capture, and shows the actual listener port while
capture is running.
Selectors use the original request's immutable rule snapshot. Automatic actions
run before each stage's manual pause; multiple matching selectors and global
breakpoints share one pending editor per message/stage. Both-stage mode pauses
the response separately after the continued request receives it. Replay skips
manual pauses. MCP rule/write permissions and the desktop-only pending editor
boundary are unchanged.
Each pause lasts up to 60 seconds before aborting; a client may time out sooner.
Closing the editor keeps the message paused. Stopping capture aborts waiting
messages. The automatic demo batch refuses matching pause rules; use your own
test client through the proxy to exercise interactive editing.
Workflow, matching and rule format
and recorded verification
describe the exact semantics and test boundaries.
Upgrade and platform notes
Back up important captures before upgrading. The new persisted pause action
requires this version. Before downgrading, remove/convert pause rules using the
new version or restore your pre-upgrade data backup; disabling them is insufficient.
Packages target macOS arm64, Windows x64 and Linux x64, with source ZIP, per-platform
build manifests and SHA-256 checksums. Check SHA256SUMS.txt and the manifest's
source commit. macOS is ad-hoc signed without Apple notarization. Intel macOS is
unverified; Windows/Linux interactive and device behavior remain experimental.
Build/headless coverage does not establish those interactive workflows.
Large response streaming is separate work: bodies above 16 MiB are still rejected,
so large video transfers can fail. WebSocket frames, trailers, HTTP/3 and existing
capture limits are unchanged. Optional native Frida binaries remain excluded and
can be installed separately with the included setup helper.
The compatible GLib 0.18.5 dependency retains the precise upstream iterator
backport and source provenance.
Version-based scanners may still report RUSTSEC-2024-0429; cargo-audit's exclusion
of path packages is not evidence of the fix. No unrelated dependency migration
or production archive-throughput improvement is claimed.
AGPL-3.0-or-later. Third-party notices remain included.