⚡ TeleDOM v4.1
🧠 Temporal Browser Intelligence Engine + Agent-Owned Workflow Runtime · 350 Certified MCP Tools for Autonomous AI Agents
🌐 Language & Documentation Catalogs
- 📖 Complete 350 Tools English Catalog (Documentation)
- 🇮🇷 کاتالوگ جامع و تفصیلی ۳۵۰ ابزار به زبان فارسی
- 🇮🇷 راهنمای فارسی پروژه (README_FA.md)
- ⚡ Agent-Owned Workflows (TeleDOM Flow) — teach once · reuse forever · prove what happened
- 🐍 Python SDK — Semantic Browser Programming
- 📋 Release Notes & Verification Report
- 💡 250 Production Recipes (EXAMPLES.md) | ۲۵۰ مثال کاربردی فارسی
- 📊 Improvement Matrix (106 Improvements)
- 📈 Measured Benchmarks & Metrics
⚡ v4.1 — The Agent-Owned Workflow Runtime
TeleDOM is not the decision-maker; TeleDOM is the enabler.
The Agent is the brain. TeleDOM is the hands, eyes, memory and browser toolbox.
Teach the browser task once. Turn it into a reusable program. Run it anywhere the browser can go.
AGENT — discover · reason · write workflows · version · debug · repair · generate bots
│ MCP (Level 1: 350 tools) ──────────────┐
│ Python SDK (Level 2: semantic browser) ─┐ │
▼ ▼
TELEDOM — browser observation · primitives · target memory ·
workflow persistence · DUMB execution · evidence · replay · proof
The Golden Automation Demo
RUN #1 (explore) 5 tool calls · 2 DOM scans · 5 MCP round trips
→ agent learns: saves learned targets + writes the workflow
RUN #2 (reuse) 1 td_workflow_run call · 1 DOM scan
✔ verify_cta ✔ click_cta ✔ extract ✔ assert → SUCCESS
deterministic execution record + verbatim replay
KPIs: 80% fewer MCP round trips · 50% fewer DOM scans · replay PASS
0 unsafe-action bypass · 0 workflow corruption · 350/350 certified
44 New Production Tools in v4.1:
Browser-first, API-optional: web applications and complex SPAs without public APIs are the primary target, not the exception. The AI agent chooses its own discovery strategy (DOM → semantics → accessibility → script → coordinates) whenever abstractions fail — TeleDOM provides rock-solid, deterministic execution primitives.
⚡ Overview & TeleDOM in One Line
TeleDOM in one line: See what happened. Understand why. Simulate what-if. Fix safely. Prove the result.
TeleDOM is a production-grade Temporal Browser Intelligence Engine and universal Model Context Protocol (MCP) platform providing 350 certified tools for autonomous AI coding agents (Claude, Cursor, Antigravity, Cline, OpenAI Swarm) and frontend engineering teams.
Every important claim is backed by mathematical evidence, confidence scoring, provenance tracking, and machine-verifiable proof.
v4.1 Measured Verification Metrics (generated by npm run bench — full matrix)
🚀 Live Demo

🎬 Live Automation Demo: Autonomous AI Coding Agent driving real-time browser forensic recording, live DOM inspection, synthetic actions, and multi-turn autonomous web flows. (Watch Full 1080p Video)
📖 Table of Contents
- ⚡ v4.1 — The Agent-Owned Workflow Runtime
- ⚡ Overview & TeleDOM in One Line
- 🐍 Python SDK Quickstart
- ✨ Key Capabilities
- 💻 Dedicated Universal CLI (
dom-antigravity) - 🏗️ System Architecture
- 📁 Repository Structure
- 🤖 Model Context Protocol (MCP) 350 Tools Reference
- 🚀 Installation & Quick Start
- 🧪 Testing & Quality Verification
- 🔐 Security, Privacy & Performance
- ❓ Troubleshooting & FAQ
- 📜 License
🐍 Python SDK Quickstart
TeleDOM provides an official, zero-dependency Python SDK (sdk/python/teledom):
from teledom import Browser, Workflow
with Browser() as browser:
# 1. High-level browser control
page = browser.inspect()
browser.type("#search-box", "Autonomous Agents")
browser.click("#submit-btn")
# 2. Workflow creation & execution
wf = Workflow("triage_issues", client=browser.client)
wf.input("filter", "Issue label filter", default="bug")
wf.step("filter_step", "td_target_check", args={"selector": ".issue-row"})
wf.save(version="1.0.0")
# 3. Execute with deterministic audit record
run = wf.run({"filter": "security"})
print("Workflow run status:", run["run"]["status"])
✨ Key Capabilities
💻 Dedicated Universal CLI (dom-antigravity)
The package exposes a global CLI binary registered as dom-antigravity (with aliases mcp-dom and browser-antigravity):
# 1. Install MCP configuration & skills into current workspace (.agents)
dom-antigravity install --workspace
# Short alias:
dom-antigravity install -w
# 2. Install globally for ALL projects in Antigravity IDE
dom-antigravity install --global
# Short alias:
dom-antigravity install -g
# 3. Install into a specific target directory
dom-antigravity install --target "C:/path/to/project"
# 4. Check bridge server health & connected Chrome tabs
dom-antigravity status
# 5. Capture clean live Chrome screenshot (Full Page + Cropped Element)
dom-antigravity screenshot
# 6. Start WebSocket Bridge manually (Optional — Auto-Bridge handles this on demand)
dom-antigravity bridge
# 7. Print ready-to-use JSON configuration for Claude Desktop or Cursor
dom-antigravity config cursor
dom-antigravity config claude
🏗️ System Architecture
Dual-Environment Execution Model
TeleDOM operates cleanly across two distinct runtime environments:
-
Browser Runtime (Chrome Extension Manifest V3 / Content Script / Injected Page Context):
- Captures low-level DOM mutations using
MutationObserver. - Binds persistent
LogicalNodeIdidentifiers to live nodes viaWeakMap. - Listens to
Ctrl + Shift + Mouse Clickfor visual element picking. - Executes synthetic live actions (
click,type,hover,focus,scroll,drag). - Renders cropped element bounding boxes on HTML5 Canvas.
- Hides floating overlays during screenshot captures.
- Captures low-level DOM mutations using
-
Node.js / MCP Server Runtime (
ForensicMCPServer):- Exposes 350 JSON-RPC 2.0 MCP tools over
stdioand HTTP. - Auto-spawns and manages the WebSocket bridge on port
3847. - Powers the Temporal EventMesh kernel, Causal Engine, and Evidence Graph.
- Reconstructs virtual DOM snapshots at sub-millisecond timestamps.
- Executes counterfactual simulations, incident investigations, and formal proofs.
- Exposes 350 JSON-RPC 2.0 MCP tools over
High-Level Architecture Diagram
┌────────────────────────────────────────────────────────────────────────┐
│ AI AGENT / MCP CLIENT │
│ (Antigravity IDE / Cursor / Claude Desktop / CLI) │
└───────────────────────────────────┬────────────────────────────────────┘
│ (JSON-RPC 2.0 over stdio)
▼
┌────────────────────────────────────────────────────────────────────────┐
│ TELEDOM V4.1 MCP SERVER (350 TOOLS) │
│ ├── 144 td_* Temporal Intelligence & Workflow Runtime Tools │
│ ├── 54 dt_* Chrome DevTools Fusion Tools │
│ ├── 31 fx_* Advanced Forensic Capabilities │
│ ├── 121 Core & Live Interaction Tools │
│ └── Zero-Config On-Demand Auto-Bridge Dispatcher │
└───────────────────┬────────────────────────────────┬───────────────────┘
│ │ (WebSocket / HTTP :3847)
▼ ▼
┌───────────────────────────────┐ ┌────────────────────────────────────┐
│ WORKFLOW RUNTIME │ │ LIVE WEBSOCKET BRIDGE SERVER │
│ ├── Workflow Persistence │ │ (Port 3847 - Auto-Managed) │
│ ├── Target Memory Store │ └─────────────────┬──────────────────┘
│ ├── EventMesh & Causal Graph │ │
│ ├── Counterfactual Engine │ │ (Bi-directional JSON frames)
│ └── Verification & Proofs │ ▼
└───────────────────────────────┘ ┌────────────────────────────────────┐
│ CHROME EXTENSION (MV3) │
│ ├── Mutation Observer Engine │
│ ├── Ctrl+Shift+Click Live Picker │
│ ├── Canvas Screenshot Pipeline │
│ └── Synthetic Interaction Driver │
└────────────────────────────────────┘
📁 Repository Structure
teledom/
├── src/
│ ├── intelligence/ # Temporal Intelligence Engine (EventMesh, Causal, Proof, Incident)
│ │ └── workflow/ # v4.1 Agent-Owned Workflow Runtime (domain, executor, store, facade)
│ ├── core/ # Core recorders, sequence counters, privacy, PNG builder
│ ├── diff/ # Structural DOM diff engine (attributes, classes, styles, subtrees)
│ ├── extension/ # Chrome Extension Manifest V3 (content scripts, service worker)
│ ├── lifecycle/ # Lifecycle tracer, disappearing UI analyzer
│ ├── mcp/ # Universal MCP Server, 350 tools definition, dispatchers
│ ├── reconstruction/ # Sub-millisecond snapshot interpolation & time-travel
│ ├── storage/ # Local disk storage & indexing engine
│ └── ui/ # Observatory UI, visual state viewers
├── sdk/
│ └── python/ # Official Python SDK (BrowserController, WorkflowEngine, TargetMemory)
├── docs/
│ ├── TOOLS_CATALOG_350_EN.md # Complete English reference for all 350 tools
│ ├── TOOLS_CATALOG_350_FA.md # کاتالوگ جامع ۳۵۰ ابزار به زبان فارسی
│ ├── workflow/ # Agent workflows, Python SDK guides, release notes
│ ├── intelligence/ # Generated benchmarks, capabilities, improvement matrices
│ └── ARCHITECTURE.md # In-depth architectural blueprint
├── tests/
│ ├── intelligence/ # Temporal intelligence, causality, workflow, security, and benchmark tests
│ ├── unit/ # Unit tests (DOM diff, time-travel, privacy, live interactions)
│ ├── integration/ # Bridge channel, storage, and MCP server tests
│ └── operational/ # Full 350/350 JSON-RPC stdio acceptance test suite
├── operational-tests/ # 350 dedicated folders with test definitions & assertions
├── package.json # Version 4.1.0, scripts, dependencies
└── README.md # English documentation (this file)
🤖 Model Context Protocol (MCP) 350 Tools Reference
TeleDOM v4.1 exposes 350 production-ready JSON-RPC 2.0 tools grouped into four distinct families.
For detailed schemas, parameter documentation, and operational examples for all 350 tools:
Summary of Tool Families
🚀 Installation & Quick Start
1. Global System Installation (One-Click)
Install the global CLI and register TeleDOM into your user configuration:
npm install -g teledom
dom-antigravity install --global
2. Workspace Installation for Any Project
To enable TeleDOM for an individual project repository:
cd /path/to/your-project
npx teledom install --workspace
This creates .agents/mcp_config.json and registers the full 350-tool skill definitions into .agents/skills/.
3. Load Chrome Extension in Browser
- Open Google Chrome and navigate to
chrome://extensions/. - Enable Developer mode in the top-right corner.
- Click Load unpacked and select the
teledom/dist/extensionfolder. - The TeleDOM extension badge will appear in your toolbar.
4. Configure External AI Clients (Claude / Cursor / Cline)
Claude Desktop Configuration (claude_desktop_config.json)
{
"mcpServers": {
"teledom": {
"command": "node",
"args": ["C:/path/to/teledom/dist/server/mcp-server.js"]
}
}
}
Cursor Configuration (.cursor/mcp.json)
{
"mcpServers": {
"teledom": {
"command": "node",
"args": ["C:/path/to/teledom/dist/server/mcp-server.js"]
}
}
}
🧪 Testing & Quality Verification
TeleDOM is backed by a rigorous multi-tier testing pipeline:
# 1. Run full unit and intelligence test suite (319 tests)
npm run test:unit
# 2. Run Python SDK self-test (17 tests)
npm run test:sdk
# 3. Run full operational stdio JSON-RPC certification (350 tools)
npm run test:operational
# 4. Run deterministic benchmark matrix (10K / 100K / 1M events)
npm run bench
# 5. Run golden incident suite (1,032 scenarios)
npm run golden
# 6. Run chaos engineering injection suite
npm run chaos
# 7. Build production bundle (client, server, extension)
npm run build
🔐 Security, Privacy & Performance
- Zero-Trust Privacy Masking:
PrivacyEngineautomatically sanitizes password fields, credit card numbers (Luhn-compliant), Social Security numbers, bearer tokens, API keys, and custom CSS selectors in both recording and live inspection. - Sandboxed Virtual Replay: Reconstructed DOM environments strip inline
on*event handlers and prevent script execution, eliminating arbitrary code execution risks. - Sub-Millisecond Overhead: Low-overhead streaming observers use
requestAnimationFrameandrequestIdleCallbackthrottling to ensure zero dropped frames on 120 Hz displays. - Clean Compositor Framing: Overlay hiding ensures pristine, unpolluted visual screenshots during automation.
❓ Troubleshooting & FAQ
Q: Do I need to run npm run bridge in a separate terminal?
A: No!
ForensicMCPServerincludes a zero-config auto-bridge. Whenever an AI agent connects via MCP, the server automatically initializes the WebSocket bridge on port3847in the background.
Q: How do I test capturing a real Chrome screenshot from the terminal?
A: Run
dom-antigravity screenshot. It connects to your active Chrome tab, captures a pristine full-page screenshot and cropped element screenshot, and saves them to disk.
Q: How are the 350 tools documented?
A: Every single tool is documented with full parameter schemas, TypeScript interfaces, and concrete operational JSON-RPC examples in TOOLS_CATALOG_350_EN.md and TOOLS_CATALOG_350_FA.md.
📜 License
Licensed under the Apache License, Version 2.0. See the LICENSE file for complete terms:
http://www.apache.org/licenses/LICENSE-2.0