knock

Tracking since May 19, 2026.

Changelog

• Jun 7, 2026
  description

  knock — fetch / XHR control inside Chrome DevTools
  
  📖 Docs, screenshots, live demos: https://knock.racgoo.com
  
  A DevTools panel that sits between your page and the network. Capture every fetch and XMLHttpRequest, rewrite them on the fly with rule pipelines, or pause a request and finish it by hand from an in-page floating editor.
  
  Runs entirely in your browser. No account, no telemetry, no server.
  
  — Capture every fetch / XHR with method, URL, status, headers, body. Detail pane shows the post-modify state.
  — Rule pipelines rewrite outgoing requests (headers / query / body / cookies — Override or Replace) and synthesize responses (status / headers / body / delay / Set-Cookies). Rules run in order.
  — Pause either side and edit live in a draggable in-page editor.
  — Real cookies through chrome.cookies — actual jar state, not a fake header.
  — Scenarios bundle rules with domain allowlists. Export / import as JSON.
  
  → Get started: https://knock.racgoo.com/docs/getting-started

  knock — drive the browser directly from Chrome DevTools
  
  📖 Docs, screenshots, live demos: https://knock.racgoo.com
  
  A DevTools panel that drives the browser end-to-end. Intercept every fetch and XMLHttpRequest, rewrite them on the fly with rule pipelines, pause a request and hand-edit it in a floating in-page editor, or record click / fill / submit flows and replay them deterministically — all from one panel.
  
  Runs entirely in your browser. No account, no telemetry, no server.
  
  — Capture every fetch / XHR with method, URL, status, headers, body. Detail pane shows the post-modify state.
  — Rule pipelines rewrite outgoing requests (headers / query / body / cookies — Override or Replace) and synthesize responses (status / headers / body / delay / Set-Cookies). Rules run in order.
  — Pause either side and edit live in a draggable in-page editor.
  — Record click / fill / submit / wait flows in the Automation tab. Replay deterministically against captured network, or fire live against the real backend for auto-login / repeat-task helpers.
  — Real cookies through chrome.cookies — actual jar state, not a fake header.
  — Rule Sets bundle rules with domain allowlists. Export / import as JSON.
  
  → Get started: https://knock.racgoo.com/docs/getting-started

• Jun 1, 2026
  description

  knock is a Chrome DevTools extension for frontend developers. It intercepts the current tab's fetch and XMLHttpRequest traffic so you can record every request, define rule pipelines, modify outgoing requests, synthesize responses, inject cookies, or pause either side and finish it from an in-page floating editor.
  
  Everything runs locally on your machine. No data leaves the browser.
  
  WHAT YOU CAN DO
  
  • Record every fetch and XHR call with method, URL, captured time, response status, headers, and body — Request and Response detail panels show the post-modify state, matching what Chrome's Network tab logged.
  • Build rule pipelines. Every matched rule runs in list order (Express middleware style), so later rules see earlier rules' output. Drag to reorder; a #N badge shows each rule's position.
  • Modify outgoing requests: headers, query params, body, cookies. Each field has an Original / Override / Replace mode so you choose how the rule blends with the page's value.
  • Synthesize responses: status, headers, body, delay, and persistent Set-Cookies.
  • Pause and edit live. A draggable, resizable in-page floating editor lets you craft the request (or response) by hand and accept it. Multiple pause windows can stack.
  • Inject cookies the right way. The Cookies and Set-Cookies sections route through chrome.cookies (request-scoped and restored after settle for outgoing; persistent for response-side, mirroring real Set-Cookie). The pause editor pre-populates with the live cookie jar so you edit real state.
  • Scenarios with domain allowlists. Save named rule bundles and pick one per tab; the scenario auto-disables when the tab URL isn't in its allowlist — so a "production" scenario won't accidentally fire on localhost.
  • Export / import rules as JSON.
  • Master on/off toggle in the panel header and toolbar popup detaches the interceptors entirely.

  knock — fetch / XHR control inside Chrome DevTools
  
  📖 Docs, screenshots, live demos: https://knock.racgoo.com
  
  A DevTools panel that sits between your page and the network. Capture every fetch and XMLHttpRequest, rewrite them on the fly with rule pipelines, or pause a request and finish it by hand from an in-page floating editor.
  
  Runs entirely in your browser. No account, no telemetry, no server.
  
  — Capture every fetch / XHR with method, URL, status, headers, body. Detail pane shows the post-modify state.
  — Rule pipelines rewrite outgoing requests (headers / query / body / cookies — Override or Replace) and synthesize responses (status / headers / body / delay / Set-Cookies). Rules run in order.
  — Pause either side and edit live in a draggable in-page editor.
  — Real cookies through chrome.cookies — actual jar state, not a fake header.
  — Scenarios bundle rules with domain allowlists. Export / import as JSON.
  
  → Get started: https://knock.racgoo.com/docs/getting-started

• May 25, 2026
  description

  knock is a Chrome DevTools extension (Manifest V3) for frontend debugging. It patches window.fetch in the page (and mirrors XMLHttpRequest for many flows), intercepts matching traffic, and lets you record requests, define rules, modify the outgoing request, synthesize a response, or pause either side and finish it from an in-page floating editor.
  
  Features
  Requests tab — live list of intercepted calls with method, URL, status, timing, and a detail pane (headers, body preview, rule/action context where applicable).
  Rules tab — ordered rules with URL + method matching and two independent action sides: a Request action and a Response action, each none / modify / pause.
  Scenarios — save and load the active rule set to chrome.storage (named presets in the panel).
  Export / import — share rule sets as JSON: Export copies or downloads the current rules; Import takes a paste or a file and either appends to or replaces your rules (imported rules get fresh ids, so they never collide).
  On / off switch — a master toggle (in the panel header) pauses all interception: the content scripts detach from window.fetch / XMLHttpRequest entirely — nothing is captured or overridden — and reattach when you switch it back on. The state is global and persists.
  Pass-through fields (fetch) — for a Response → modify action, pick whether status, headers, body, and delay come from your editor, from the real network response, or are merged (headers/body can overlay server values on fetch).

  knock is a Chrome DevTools extension for frontend developers. It intercepts the current tab's fetch and XMLHttpRequest traffic so you can record every request, define rule pipelines, modify outgoing requests, synthesize responses, inject cookies, or pause either side and finish it from an in-page floating editor.
  
  Everything runs locally on your machine. No data leaves the browser.
  
  WHAT YOU CAN DO
  
  • Record every fetch and XHR call with method, URL, captured time, response status, headers, and body — Request and Response detail panels show the post-modify state, matching what Chrome's Network tab logged.
  • Build rule pipelines. Every matched rule runs in list order (Express middleware style), so later rules see earlier rules' output. Drag to reorder; a #N badge shows each rule's position.
  • Modify outgoing requests: headers, query params, body, cookies. Each field has an Original / Override / Replace mode so you choose how the rule blends with the page's value.
  • Synthesize responses: status, headers, body, delay, and persistent Set-Cookies.
  • Pause and edit live. A draggable, resizable in-page floating editor lets you craft the request (or response) by hand and accept it. Multiple pause windows can stack.
  • Inject cookies the right way. The Cookies and Set-Cookies sections route through chrome.cookies (request-scoped and restored after settle for outgoing; persistent for response-side, mirroring real Set-Cookie). The pause editor pre-populates with the live cookie jar so you edit real state.
  • Scenarios with domain allowlists. Save named rule bundles and pick one per tab; the scenario auto-disables when the tab URL isn't in its allowlist — so a "production" scenario won't accidentally fire on localhost.
  • Export / import rules as JSON.
  • Master on/off toggle in the panel header and toolbar popup detaches the interceptors entirely.

• May 25, 2026
  short_description

  HTTP fetch interceptor for frontend debugging

  Intercept, modify, or pause fetch/XHR in any page. Rule-based response overrides, cookie injection, and in-page live editing.

• May 25, 2026
  permissions

  storage

  storage, cookies

Permissions & access

Permissions

storagecookies

Host access

<all_urls>

Screenshots