deep-web-research

Deep Web Research with Kimi WebBridge

When to Use

• User asks for "deep research", "comprehensive research", "investigate thoroughly"
• Multi-source investigation needed (GitHub, X/Twitter, Google, docs sites)
• Need 10+ tabs organized in named tab groups
• User says "retry" to re-do with same approach

Core Methodology

1. Session & Tab Group Setup

# First navigate: create session + tab group with human-readable label
curl -s -X POST http://127.0.0.1:10086/command \
  -H 'Content-Type: application/json' \
  -d '{"action":"navigate","args":{"url":"<first_url>","newTab":true,"group_title":"<descriptive label>"},"session":"<task-name>"}'

Rules:

• One task = one session = one tab group
• Session name = task identifier (e.g., vsouthvpawv-research, web-search)
• group_title = user-language label shown in browser tab group
• Never switch session names mid-task

2. Opening Additional Sources

# Subsequent navigates: same session, newTab:true, no group_title needed
curl -s -X POST http://127.0.0.1:10086/command \
  -H 'Content-Type: application/json' \
  -d '{"action":"navigate","args":{"url":"<url>","newTab":true},"session":"<task-name>"}'

3. Reading Page Content

# Snapshot returns accessibility tree with @e refs
curl -s -X POST http://127.0.0.1:10086/command \
  -H 'Content-Type: application/json' \
  -d '{"action":"snapshot","args":{},"session":"<task-name>"}'

4. Following Links / Interacting

• Use @e refs from snapshot for click/fill
• Prefer snapshot over CSS selectors
• For navigation, use navigate with same session

Proper Use of @e References

Important: The @e references (e.g., @e58, @e100) returned by the snapshot tool are special identifiers that work ONLY as direct values for the selector parameter in tools like click, fill, etc.

Common Mistake

Attempting to use @e references in evaluate() with DOM query methods will FAIL:

// ❌ WRONG - This will throw "Failed to execute 'querySelector' on 'Document': '@e58' is not a valid selector"
document.querySelector("@e58").href