Skip to main content

Documentation Index

Fetch the complete documentation index at: https://webscraping.titannet.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

They are implemented across the titan-agent repository and the webscraping-backend stack. Unlike browser nodes, these workers execute inside a browser extension environment and receive work through extension-oriented backend services.

​
What this worker model does

The extension worker model is designed around:
  • Extension bootstrap and configuration
  • Discovery of backend entry points
  • Device registration and authentication
  • WebSocket-based task delivery
  • Browser page interaction through injected scripts
  • Task result reporting back to the server layer

​
High-level lifecycle

At a high level, the extension worker flow is:
  1. Discover available backend endpoints
  2. Select a harbor or active backend
  3. Authenticate and register the device
  4. Open a WebSocket connection
  5. Receive job updates and task commands
  6. Inject and execute scraping scripts inside browser pages
  7. Report task status and output back to the server

​
Platform verification

A key part of this worker model is platform verification. The extension stack can require a device to be verified for a specific platform before it receives production work for that platform. This makes the extension path different from generic browser automation workers and reflects its closer relationship to an active browser environment.

​
Why this worker type is documented separately

The extension path is not just another runtime for the same orchestration loop. It uses a different control model, different delivery mechanism, and a different operational backend. That is why it should be documented as a separate worker architecture, even though it serves the same broad scraping purpose.

​
When this model is useful

This worker model is most useful when the platform needs execution inside a browser extension context rather than a standalone automation node.

​
Next steps