mirror of
https://github.com/BaaRai/ARTEX.git
synced 2026-11-13 11:40:53 +08:00
Closes #33. The MITM proxy only sees the agent's own actions, so anything behind a human gate (signup captcha, email OTP, 2FA, SSO) left the authenticated surface dark. The operator's browser becomes a capture source instead: - traffic: exported RecordExternal storing an externally captured exchange through the same spill/blob/FTS path as proxy traffic (insert logic shared with record()); rejects unparsable URLs and empty methods - server: POST /api/traffic/ingest inside the authenticated API group, batch capped at 50 entries, bodies truncated at 256 KiB, per-entry ingested/failed counts - extension/: Manifest V3 Chrome/Edge extension driving the chrome.debugger Network domain on the chosen tab, batching text exchanges to the ingest endpoint with the operator's URL + JWT in chrome.storage.local; binary bodies skipped; flush on batch/stop - tests for both layers, README section
11 lines
485 B
JSON
11 lines
485 B
JSON
{
|
|
"manifest_version": 3,
|
|
"name": "ARTEX Traffic Capture",
|
|
"version": "1.0.0",
|
|
"description": "Capture the current tab's network traffic into your local ARTEX instance, so operator-driven authenticated browsing becomes agent-visible evidence.",
|
|
"permissions": ["debugger", "storage", "tabs"],
|
|
"host_permissions": ["<all_urls>"],
|
|
"background": { "service_worker": "background.js" },
|
|
"action": { "default_popup": "popup.html", "default_title": "ARTEX Traffic Capture" }
|
|
}
|