Compare commits

...
Author SHA1 Message Date
leeguooooo 96ee2f9758 chore(release): 0.27.0-fork.41 — relay self-heals silently (no user action on blip)
Release binaries / Build macOS ARM64 (push) Has been cancelled
Release binaries / Build macOS x64 (push) Has been cancelled
Release binaries / Build Linux ARM64 (push) Has been cancelled
Release binaries / Build Linux musl ARM64 (push) Has been cancelled
Release binaries / Build Linux musl x64 (push) Has been cancelled
Release binaries / Build Linux x64 (push) Has been cancelled
Release binaries / Build Windows x64 (push) Has been cancelled
Release binaries / Attach binaries to GitHub Release (push) Has been cancelled
2026-06-11 21:30:38 +09:00
leeguooooo 0a3d2a91a6 fix(connect): self-heal the relay silently — ~15s retry, no user action
fork.40 errored after 5s ("reload the extension"), which still pushed the problem
onto the user. Extend the relay-reconnect wait to ~15s when the extension is
installed: enough for the MV3 service worker to wake and reconnect on its own
(onStartup after a Chrome restart, or the keepalive alarm). The loop re-checks
the relay file each iteration, so a mid-wait recovery is picked up instantly and
the full window is only spent when the extension is genuinely down. End users no
longer have to do anything when the relay blips.
2026-06-11 21:30:37 +09:00
leeguooooo 1e5dfd35cb chore(release): 0.27.0-fork.40 — no consent-dialog fallback when extension is installed
Release binaries / Build macOS ARM64 (push) Has been cancelled
Release binaries / Build macOS x64 (push) Has been cancelled
Release binaries / Build Linux ARM64 (push) Has been cancelled
Release binaries / Build Linux musl ARM64 (push) Has been cancelled
Release binaries / Build Linux musl x64 (push) Has been cancelled
Release binaries / Build Linux x64 (push) Has been cancelled
Release binaries / Build Windows x64 (push) Has been cancelled
Release binaries / Attach binaries to GitHub Release (push) Has been cancelled
2026-06-11 21:17:03 +09:00
leeguooooo b6b2ca56ca fix(connect): never fall back to the consent-dialog raw port when the extension is installed
Root cause of the recurring "Allow remote debugging?" dialog: when the ab-connect
relay was momentarily down (MV3 service worker drops the relay-url file across a
Chrome restart / idle wake), auto_connect_cdp silently fell through to the raw
:9222 DevToolsActivePort path — which pops Chrome 136+'s consent modal, the exact
thing the extension exists to avoid. Even a relay-aware build hit this if it
connected during the blip.

Fix: if the native-messaging host is installed (connect::host_installed() — the
durable signal that the user chose the extension path), auto_connect retries the
relay for ~5s while the SW reconnects, and then ERRORS with an actionable message
instead of attaching to a raw debug port. The raw :9222 path now runs only when
no extension is set up (where the dialog is expected). `--cdp <port>` still forces
the raw path explicitly.
2026-06-11 21:17:02 +09:00
leeguooooo 6d740093dc chore(release): 0.27.0-fork.39 — cookies set --curl preserves full attributes
Release binaries / Build macOS ARM64 (push) Has been cancelled
Release binaries / Build macOS x64 (push) Has been cancelled
Release binaries / Build Linux ARM64 (push) Has been cancelled
Release binaries / Build Linux musl ARM64 (push) Has been cancelled
Release binaries / Build Linux musl x64 (push) Has been cancelled
Release binaries / Build Linux x64 (push) Has been cancelled
Release binaries / Build Windows x64 (push) Has been cancelled
Release binaries / Attach binaries to GitHub Release (push) Has been cancelled
2026-06-11 21:09:04 +09:00
leeguooooo c884fb4f57 fix(cookies): preserve full cookie attributes in cookies set --curl JSON import
The JSON-array branch of parse_curl_cookies dropped every field except
name/value, so importing a full cookie export (httpOnly session tokens,
per-domain cookies spanning multiple hosts, secure/sameSite/expiry) could
not reconstruct a usable auth state — a single --domain override cannot
cover an export that spans .chatgpt.com, .openai.com, etc.

Pass through url/domain/path/secure/httpOnly/sameSite/expires when present,
accepting common aliases from DevTools / EditThisCookie exports
(http_only, same_site, no_restriction, expirationDate). Bare {name,value}
exports are unchanged. Added a round-trip test.
2026-06-11 21:09:04 +09:00
leeguooooo 57ef011817 docs: document humanize (human-like input) + silent operation
- README + README.zh: new Anti-detection subsections — "Human-like input
  (behavioural stealth)" (curved trajectories / jitter / cadence / eased
  scroll-drag, adaptive per-page escalation, off|fast|human) with the
  trajectory contrast table, and "Silent operation" (background tabs, no
  foreground stealing, focus-emulated). Added AGENT_BROWSER_HUMANIZE to the
  tuning-knobs table.
- skill core: agents told operation is silent by default and how/when to use
  --humanize (leave on auto; force human for known behavioural targets).
2026-06-11 21:04:35 +09:00
leeguooooo 2c3bcb8f3d chore(release): 0.27.0-fork.38 — silent operation (no foreground tab stealing)
Release binaries / Build macOS ARM64 (push) Has been cancelled
Release binaries / Build macOS x64 (push) Has been cancelled
Release binaries / Build Linux ARM64 (push) Has been cancelled
Release binaries / Build Linux musl ARM64 (push) Has been cancelled
Release binaries / Build Linux musl x64 (push) Has been cancelled
Release binaries / Build Linux x64 (push) Has been cancelled
Release binaries / Build Windows x64 (push) Has been cancelled
Release binaries / Attach binaries to GitHub Release (push) Has been cancelled
2026-06-11 20:12:28 +09:00
leeguooooo 5a61a64559 feat(stealth): silent operation — never steal the user's foreground tab
Driving the user's real Chrome should not yank their view around. Now the agent
operates entirely in the background:
- New tabs are created with `background: true` (CreateTargetParams) so opening
  one never foregrounds it (the ab-connect extension already used active:false;
  this covers the raw-CDP path too).
- Dropped the two AUTO `Page.bringToFront` calls (auto-connect fresh tab, and the
  internal active-page switch). The explicit `bringToFront` command is untouched —
  surfacing a tab stays opt-in.
- enable_domains now sets `Emulation.setFocusEmulationEnabled(true)` so a
  backgrounded agent tab still renders (screenshots work), isn't render-throttled,
  and reports document.hasFocus()/visibilityState='visible' — which also removes
  the "tab is hidden the whole session" bot tell.

Verified headless: hasFocus=true/visible while backgrounded; click + screenshot
still work. Default behaviour, no flag.
2026-06-11 20:11:22 +09:00
13 changed files with 219 additions and 20 deletions
+20
View File
@@ -227,6 +227,25 @@ When connected to your real Chrome, we inject **zero** JavaScript patches. Your
When using `--launch` mode (standalone browser), a full suite of stealth patches is applied instead, and it still passes the suite above.
### Human-like input (behavioural stealth)
Fingerprint stealth isn't the whole story — the strongest anti-bot vendors (Akamai, PerimeterX, DataDome) also score *behaviour*. A click that teleports the cursor to an element's exact centre with no approach path and zero press delay is a tell, **even though our CDP events are `isTrusted`**.
With humanize on, the cursor moves like a hand: clicks follow a curved, decelerating Bézier path and land on a jittered point *inside* the element (never the dead centre); typing uses variable inter-keystroke timing; scrolling eases in segments; drags follow a curve. It's **adaptive** — every navigation is probed for known anti-bot vendors (cookies / scripts / globals) and a guarded page auto-escalates to full human motion, while ordinary sites stay instant (zero overhead).
What the page's own `mousemove` stream sees (this *is* what a behavioural detector analyses):
| | trajectory |
|---|---|
| **off** (default) | straight lines · dead-centre · instant |
| **human** | curved trails · slow-in/slow-out · off-centre landings |
Control with `--humanize off\|fast\|human` or `AGENT_BROWSER_HUMANIZE`. Default `off`; the adaptive detector escalates per page.
### Silent operation
Driving your real Chrome should never interrupt your work. The agent operates **entirely in the background**: new tabs open un-focused (in their own colored per-session tab group), the agent **never force-fronts a tab**, and `Emulation.setFocusEmulationEnabled` keeps each agent tab rendering and reporting `document.hasFocus()` / `visibilityState: 'visible'`. So screenshots still work, pages aren't render-throttled, and "the tab was hidden the whole session" never becomes its own bot tell. You keep working in your active tab; the agent works alongside you, silently. (Surfacing a tab stays available as an explicit command.)
### Verify it yourself
Don't take our word for it — point your connected Chrome at the toughest public detectors and compare:
@@ -244,6 +263,7 @@ We deliberately **don't ship our own bot detector** — the strongest, most hone
| Variable | Default | Effect |
|---|---|---|
| `AGENT_BROWSER_CAPTURE_CONSOLE` | off | Enable `Runtime` domain so `console` / `errors` capture page output. Off keeps the stealthiest profile. |
| `AGENT_BROWSER_HUMANIZE` | off | Human-like input motion: `off` (instant), `fast` (light eased trajectory), `human` (full curved trajectory + landing jitter + typing cadence + eased scroll/drag). Also `--humanize`. Default `off`; the adaptive detector auto-escalates pages guarded by Akamai/PerimeterX/DataDome to `human`. |
| `AGENT_BROWSER_TIMEZONE` | unset | `--launch` only. An IANA id (e.g. `Asia/Tokyo`) sets the timezone natively (Intl + Date follow, no JS lie) to match a proxy; `auto` derives one from the locale. |
| `AGENT_BROWSER_BLOCK_WEBRTC` | auto | `--launch` only. Auto-forces WebRTC through the proxy when one is set (no real-IP leak). `1` hides the local IP without a proxy; `0` opts out. |
| `AGENT_BROWSER_HIDE_CANVAS` | off | `--launch` only. Adds session-stable canvas/audio fingerprint noise. Off by default (noise is itself a "lie"). |
+19
View File
@@ -148,6 +148,25 @@ agent-browser --launch --profile auto open https://x.com/home
`--launch` 独立模式下会改用一整套隐身补丁,同样过上述检测。
### 类人输入(行为隐身)
指纹隐身只是一半——最强的反爬厂商(Akamai、PerimeterX、DataDome)还会给**行为**打分。点击时光标瞬移到元素正中心、没有接近轨迹、按下即抬起,这本身就是破绽,**哪怕我们的 CDP 事件是 `isTrusted`**。
开启 humanize 后,光标像手在动:点击走带减速的贝塞尔曲线、落在元素内**偏离正中心**的抖动点;打字用变速的击键间隔;滚动分段缓动;拖拽走曲线。而且**自适应**——每次导航探测页面是否有已知反爬厂商(cookie/脚本/全局变量),命中就自动升到全套类人动作,普通站点保持瞬时(零开销)。
页面自己的 `mousemove` 流看到的(行为检测器分析的正是这个):
| | 轨迹 |
|---|---|
| **off**(默认) | 直线 · 死磕正中心 · 瞬时 |
| **human** | 曲线 · 先慢后快再慢 · 落点偏移 |
`--humanize off\|fast\|human``AGENT_BROWSER_HUMANIZE` 控制。默认 `off`,自适应检测器按页面自动升档。
### 静默操作
操作你的真实 Chrome 不该打断你的工作。agent **全程在后台操作**:新标签后台打开(在自己的彩色会话标签组里),**从不强制把标签拽到前台**,并用 `Emulation.setFocusEmulationEnabled` 让每个 agent 标签照常渲染、`document.hasFocus()` / `visibilityState` 仍报 `visible`。于是截图正常、页面不被降频,"标签全程隐藏"也不会变成新的机器人信号。你在自己的标签里照常工作,agent 在旁边默默干活。(想置顶某个标签仍可显式调用命令。)
## 与上游的差异
基于 [agent-browser v0.27.0](https://github.com/vercel-labs/agent-browser)
+1 -1
View File
@@ -45,7 +45,7 @@ dependencies = [
[[package]]
name = "agent-browser-stealth"
version = "0.27.0-fork.37"
version = "0.27.0-fork.41"
dependencies = [
"aes-gcm",
"async-trait",
+1 -1
View File
@@ -1,6 +1,6 @@
[package]
name = "agent-browser-stealth"
version = "0.27.0-fork.37"
version = "0.27.0-fork.41"
edition = "2021"
description = "Fast browser automation CLI for AI agents"
license = "Apache-2.0"
+80 -1
View File
@@ -101,7 +101,62 @@ pub fn parse_curl_cookies(raw: &str) -> Result<Vec<Value>, String> {
.get("value")
.and_then(|v| v.as_str())
.ok_or_else(|| format!("cookies[{}] missing string value", i))?;
out.push(json!({ "name": name, "value": value }));
let mut cookie = json!({ "name": name, "value": value });
let obj = cookie.as_object_mut().unwrap();
// Preserve any CDP Network.setCookie attributes present on the
// source object so a full auth state round-trips: httpOnly session
// tokens, per-domain cookies (a single export spans .chatgpt.com,
// .openai.com, ...), and secure/sameSite/expiry. A bare
// {name,value} export is unchanged. Common aliases from DevTools /
// EditThisCookie / extension exports are accepted.
if let Some(v) = c.get("url").and_then(|v| v.as_str()) {
obj.insert("url".into(), json!(v));
}
if let Some(v) = c.get("domain").and_then(|v| v.as_str()) {
obj.insert("domain".into(), json!(v));
}
if let Some(v) = c.get("path").and_then(|v| v.as_str()) {
obj.insert("path".into(), json!(v));
}
if let Some(v) = c.get("secure").and_then(|v| v.as_bool()) {
obj.insert("secure".into(), json!(v));
}
if let Some(v) = c
.get("httpOnly")
.or_else(|| c.get("httponly"))
.or_else(|| c.get("http_only"))
.and_then(|v| v.as_bool())
{
obj.insert("httpOnly".into(), json!(v));
}
if let Some(v) = c
.get("sameSite")
.or_else(|| c.get("samesite"))
.or_else(|| c.get("same_site"))
.and_then(|v| v.as_str())
{
let norm = match v.to_lowercase().as_str() {
"strict" => "Strict",
"lax" => "Lax",
"none" | "no_restriction" => "None",
_ => "",
};
if !norm.is_empty() {
obj.insert("sameSite".into(), json!(norm));
}
}
// CDP `expires` is seconds since the Unix epoch (f64). Accept
// `expires` or EditThisCookie's `expirationDate`.
if let Some(v) = c
.get("expires")
.or_else(|| c.get("expirationDate"))
.and_then(|v| v.as_f64())
{
if v > 0.0 {
obj.insert("expires".into(), json!(v));
}
}
out.push(cookie);
}
return Ok(out);
}
@@ -2859,6 +2914,27 @@ mod tests {
assert_eq!(cmd["action"], "cookies_clear");
}
#[test]
fn test_parse_curl_cookies_json_preserves_attributes() {
// A full cookie export (httpOnly session token, per-domain, secure,
// sameSite, expiry) must round-trip — not get flattened to name/value.
let input = r#"[
{"name":"__Secure-next-auth.session-token","value":"eyJ.tok","domain":".chatgpt.com","path":"/","secure":true,"httpOnly":true,"sameSite":"Lax","expires":1893456000},
{"name":"cf_clearance","value":"abc","domain":".openai.com","path":"/","secure":true,"http_only":true,"same_site":"no_restriction"}
]"#;
let out = parse_curl_cookies(input).unwrap();
assert_eq!(out.len(), 2);
assert_eq!(out[0]["domain"], ".chatgpt.com");
assert_eq!(out[0]["secure"], true);
assert_eq!(out[0]["httpOnly"], true);
assert_eq!(out[0]["sameSite"], "Lax");
assert_eq!(out[0]["expires"], 1893456000.0);
// alias keys (http_only, same_site=no_restriction) normalize to CDP shape
assert_eq!(out[1]["domain"], ".openai.com");
assert_eq!(out[1]["httpOnly"], true);
assert_eq!(out[1]["sameSite"], "None");
}
#[test]
fn test_parse_curl_cookies_json_array() {
let input = r#"[{"name":"a","value":"1"},{"name":"b","value":"2"}]"#;
@@ -2866,6 +2942,9 @@ mod tests {
assert_eq!(out.len(), 2);
assert_eq!(out[0]["name"], "a");
assert_eq!(out[0]["value"], "1");
// bare {name,value} stays minimal — no spurious attribute keys
assert!(out[0].get("domain").is_none());
assert!(out[0].get("secure").is_none());
assert_eq!(out[1]["name"], "b");
assert_eq!(out[1]["value"], "2");
}
+13
View File
@@ -344,6 +344,19 @@ fn host_manifest_path_for_chrome() -> Option<PathBuf> {
})
}
/// True if the ab-connect native-messaging host manifest is present — i.e. the
/// user has set up the extension path. When installed, auto-connect treats the
/// dialog-free extension relay as the *intended* transport and refuses to fall
/// back to a raw debug port (which would pop Chrome 136+'s "Allow remote
/// debugging?" consent modal). The relay-url file comes and goes with the
/// service worker; this manifest is the durable signal that the extension is
/// the chosen path.
pub fn host_installed() -> bool {
native_messaging_dirs()
.into_iter()
.any(|d| d.join(format!("{HOST_NAME}.json")).exists())
}
fn report(json: bool, ok: bool, msg: &str) {
if json {
println!(
+3 -4
View File
@@ -1511,12 +1511,11 @@ pub async fn execute_command(cmd: &Value, state: &mut DaemonState) -> Value {
/// subsequent navigations don't hijack the user's existing tabs.
async fn connect_auto_with_fresh_tab() -> Result<BrowserManager, String> {
let mut mgr = BrowserManager::connect_auto().await?;
// tab_new creates the tab in the background (CreateTargetParams.background),
// so attaching to the user's Chrome never steals their foreground tab. We
// deliberately do NOT bring it to front — silent operation.
mgr.tab_new(None, None).await?;
let session_id = mgr.active_session_id()?.to_string();
let _ = mgr
.client
.send_command("Page.bringToFront", None, Some(&session_id))
.await;
// Liveness probe: confirm the CDP session can actually round-trip
// before returning success. Without this, a zombie CDP socket (process
+21 -5
View File
@@ -581,6 +581,7 @@ impl BrowserManager {
&CreateTargetParams {
url: "about:blank".to_string(),
agent_group,
background: None,
},
None,
)
@@ -687,6 +688,20 @@ impl BrowserManager {
Some(session_id),
)
.await;
// Silent operation: agent tabs are driven in the background (we never
// force them to the foreground), so emulate focus. Without this a
// backgrounded tab is render-throttled and reports `document.hidden` /
// `!document.hasFocus()` — which both breaks timing-sensitive pages and
// is itself a bot signal (a real user looks at the page). Best-effort;
// ignored on engines without Emulation support.
let _ = self
.client
.send_command(
"Emulation.setFocusEmulationEnabled",
Some(json!({ "enabled": true })),
Some(session_id),
)
.await;
Ok(())
}
@@ -973,6 +988,7 @@ impl BrowserManager {
&CreateTargetParams {
url: "about:blank".to_string(),
agent_group,
background: None,
},
None,
)
@@ -1137,6 +1153,7 @@ impl BrowserManager {
&CreateTargetParams {
url: target_url.to_string(),
agent_group,
background: Some(true),
},
None,
)
@@ -1192,11 +1209,10 @@ impl BrowserManager {
let session_id = self.pages[index].session_id.clone();
self.enable_domains(&session_id).await?;
// Bring tab to front
let _ = self
.client
.send_command("Page.bringToFront", None, Some(&session_id))
.await;
// Silent: switching the agent's *internal* active page must not yank the
// user's foreground tab. The page is driven in the background (focus is
// emulated in enable_domains); the explicit `bringToFront` command is the
// only way a tab is deliberately surfaced.
let url = self.get_url().await.unwrap_or_default();
let title = self.get_title().await.unwrap_or_default();
+39 -7
View File
@@ -783,14 +783,46 @@ pub async fn auto_connect_cdp() -> Result<String, String> {
// / :9222 probes below: if the user's Chrome happens to also be listening on a
// debug port, attaching there would pop the consent dialog and defeat the
// whole zero-interaction extension path.
if let Some(relay) = crate::connect::relay_url() {
// The relay is a local CDP-over-WS endpoint we connect to like Chrome.
// A bare TCP liveness check (no WS upgrade) confirms it is actually
// accepting before we commit, mirroring the consent-free probe used for
// DevToolsActivePort.
if relay_is_live(&relay).await {
return Ok(relay);
// If the extension is installed, it is the *intended* transport. The relay
// URL file comes and goes with the MV3 service worker (a Chrome restart or an
// idle SW briefly drops it), so a single failed probe doesn't mean "no
// extension" — retry for a few seconds while it reconnects. Crucially, when
// the extension is set up we must NEVER fall through to the raw :9222 path
// below: that pops Chrome 136+'s "Allow remote debugging?" dialog, the exact
// thing the extension exists to avoid.
// ~15s of retries (500ms apart) when the extension is installed: long enough
// for the MV3 service worker to wake and reconnect on its own (onStartup
// after a Chrome restart, or the keepalive alarm) so the relay self-heals
// with NO user action. The loop re-checks the relay file every iteration, so
// a recovery mid-wait is picked up immediately — the full window is only ever
// spent when the extension is genuinely down.
let host_installed = crate::connect::host_installed();
let relay_attempts = if host_installed { 30 } else { 1 };
for attempt in 0..relay_attempts {
if let Some(relay) = crate::connect::relay_url() {
// The relay is a local CDP-over-WS endpoint we connect to like Chrome.
// A bare TCP liveness check (no WS upgrade) confirms it is actually
// accepting before we commit, mirroring the consent-free probe used
// for DevToolsActivePort.
if relay_is_live(&relay).await {
return Ok(relay);
}
}
if host_installed && attempt + 1 < relay_attempts {
tokio::time::sleep(std::time::Duration::from_millis(500)).await;
}
}
if host_installed {
return Err(
"The agent-browser-stealth extension is installed, but its relay \
isn't connected right now. Wake it up — click the extension's \
toolbar icon, or reload it at chrome://extensions — then retry. \
(agent-browser will not attach to a raw --remote-debugging-port \
while the extension is set up, because that pops Chrome's \"Allow \
remote debugging?\" dialog. Use --cdp <port> to force the raw path.)"
.to_string(),
);
}
let user_data_dirs = get_chrome_user_data_dirs();
+6
View File
@@ -153,6 +153,12 @@ pub struct CreateTargetParams {
/// endpoint never receives an unknown parameter.
#[serde(skip_serializing_if = "Option::is_none")]
pub agent_group: Option<String>,
/// Create the tab in the background so opening it never steals the user's
/// foreground tab (silent operation). Standard CDP param; the ab-connect
/// extension creates its tabs `active: false` regardless, so this only
/// affects the raw-CDP (no extension) path.
#[serde(skip_serializing_if = "Option::is_none")]
pub background: Option<bool>,
}
#[derive(Debug, Deserialize)]
+1
View File
@@ -121,6 +121,7 @@ async fn collect_storage_via_temp_target(
url: "about:blank".to_string(),
// Transient internal target (storage collection) — never grouped.
agent_group: None,
background: None,
},
None,
)
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "agent-browser-stealth",
"version": "0.27.0-fork.37",
"version": "0.27.0-fork.41",
"description": "Browser automation CLI for AI agents — stealth fork with anti-detection",
"type": "module",
"packageManager": "pnpm@11.1.3",
+14
View File
@@ -102,6 +102,20 @@ connect) > a headed launched browser > headless (forbidden).** A genuine human
browser has no headless/automation tells at all, so prefer it for anything
anti-bot-sensitive.
**Silent by default.** When driving the user's real Chrome the agent works
entirely in the background — new tabs open un-focused, the agent never force-
fronts a tab, and focus is emulated so the page still renders and reports
`visibilityState: 'visible'`. You don't need to do anything; just don't expect
the user's view to follow you (use the explicit `bringToFront` only if you
deliberately want to surface a tab).
**Human-like input for behavioural anti-bot.** Beyond fingerprint stealth,
`--humanize off|fast|human` (or `AGENT_BROWSER_HUMANIZE`) makes clicks follow a
curved, decelerating path with in-element landing jitter, typing use variable
cadence, and scroll/drag ease. Default `off`; a per-navigation detector
auto-escalates pages guarded by Akamai/PerimeterX/DataDome to `human`. Leave it
on auto; force `human` only when you already know the target scores behaviour.
## Two ways to drive a page — and when to drop to `eval`
You have a **real Chrome with the user's DOM**. Two layers, mix them freely: