How Webcmd Works
Webcmd gives an agent a live browser plus memory of website structure. The agent completes the task against the current page while preserving useful, verified context for the next run.The Agent’s Decision Flow
- Create a named browser Session in the requested Profile.
- Use relevant site memory as a starting point when it is available.
- Inspect the live page before relying on remembered structure.
- Navigate, extract, and verify the requested result.
- Retain useful structural knowledge for future browser tasks.
Live Pages Stay Authoritative
Memory helps an agent find likely pages, controls, and content regions without repeating every discovery step. It is guidance, not a recording or a fixed script. When the page differs from memory, the agent follows the live page and updates its understanding.Profiles, Sessions, and Tabs
A Profile is a browser identity and storage boundary, such asdefault or
work. Use separate Profiles for accounts or environments that must not share
sign-in state.
A Session is a named browser workspace inside a Profile. Sessions allow
separate agents or tasks to work without competing for the same browser window.
Its readable ID is immutable and scoped to its Profile.