[OneDev #12] research: Camofox — anti-detection browser for AI agents (Camoufox-powered) #26

Closed
opened 2026-05-24 04:46:39 +00:00 by joseph · 1 comment
Owner

Imported from OneDev issue #12 (id 35278)
Original project: internal-joseph
Original state: Closed
Original submitterId: 5
Original submitDate: 2026-04-10T17:07:13.222+00:00
Original lastActivity: {'date': '2026-04-18T12:52:39.405+00:00', 'description': "changed state to 'Closed'", 'userId': 5}

Original fields:

  • Type: New Feature
  • Priority: Normal
  • Assignees: None

Idea

Evaluate Camofox (https://github.com/jo-inc/camofox-browser) as a potential browser automation layer for AI agents. Built on Camoufox, it spoofs browser fingerprints to avoid bot detection — relevant for client portal automation (INKY, AT, etc.) where Playwright gets blocked.

Why

Lab Phase 2 (Lightpanda on VMID 128) works for static sites but fails on JS-heavy portals. Camofox's anti-detection layer could unlock automation of vendor portals that actively block headless browsers. Directly relevant to int-saas-k1-exclaimer#2 and future client onboarding scripts.

Open questions

  • How does it compare to Lightpanda and dev-browser from Lab Phase 1?
  • Does it expose an MCP interface or require a custom wrapper like Lightpanda?
  • Python or Node.js driver?
Imported from OneDev issue #12 (id 35278) Original project: internal-joseph Original state: Closed Original submitterId: 5 Original submitDate: 2026-04-10T17:07:13.222+00:00 Original lastActivity: {'date': '2026-04-18T12:52:39.405+00:00', 'description': "changed state to 'Closed'", 'userId': 5} Original fields: - Type: New Feature - Priority: Normal - Assignees: None ## Idea Evaluate Camofox (https://github.com/jo-inc/camofox-browser) as a potential browser automation layer for AI agents. Built on Camoufox, it spoofs browser fingerprints to avoid bot detection — relevant for client portal automation (INKY, AT, etc.) where Playwright gets blocked. ## Why Lab Phase 2 (Lightpanda on VMID 128) works for static sites but fails on JS-heavy portals. Camofox's anti-detection layer could unlock automation of vendor portals that actively block headless browsers. Directly relevant to int-saas-k1-exclaimer#2 and future client onboarding scripts. ## Open questions - How does it compare to Lightpanda and dev-browser from Lab Phase 1? - Does it expose an MCP interface or require a custom wrapper like Lightpanda? - Python or Node.js driver?
Author
Owner

Imported from OneDev comment id 375 on issue #12
Original userId: 5
Original date: 2026-04-18T12:52:38.405+00:00

Covered by int-lab#9, which is the perpetual agent browser workshop and already included Camofox in its original sweep (desk-researched, Tier-2 watchlist verdict). A full Phase-1 Docker smoke test is now running against the 25-point rubric — results will be posted to int-lab#9 directly. No separate tracking needed here.

Imported from OneDev comment id 375 on issue #12 Original userId: 5 Original date: 2026-04-18T12:52:38.405+00:00 Covered by int-lab#9, which is the perpetual agent browser workshop and already included Camofox in its original sweep (desk-researched, Tier-2 watchlist verdict). A full Phase-1 Docker smoke test is now running against the 25-point rubric — results will be posted to int-lab#9 directly. No separate tracking needed here.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
joseph/internal-joseph#26
No description provided.