In designCompany-specific agents
Each company’s agent is grounded in that company’s own documentation, products and support history, not generic advice.
Open decision: retrieval over approved company material versus fine-tuning or dedicated models. Each carries different cost, isolation and maintenance trade-offs.
Concept demoBrowser-first sessions
A support page the customer opens in their browser. The agent gets scoped, visible, revocable access before anything is ever installed.
The animated walkthrough on this site shows the intended consent and approval flow. It does not access your device.
In designWhole-session context
The agent sees the whole shared session, not isolated form fields, so it can diagnose what is really happening.
Seeing a full screen makes on-screen content an attack surface. Everything the agent reads is treated as untrusted data.
In designHuman-reviewed learning
A fix the agent discovers is a candidate. It becomes trusted knowledge only after a person reviews and approves it.
Generalising a fix without carrying one customer’s private data into another’s agent is a hard requirement, not a later improvement.
Concept demoHonest escalation
When the agent can’t finish, it hands over a clear report: what it saw, what it tried, and why it stopped.
You can download an illustrative sample report from the concept walkthrough.
PlannedCompanion apps
Desktop and mobile apps for cases a browser can’t reach: deeper OS access, an unresponsive device, or a phone camera for physical products.
Built only where browser-first genuinely falls short, and bound by the same consent rules.
PlannedCross-device handoff
Move an in-progress session from one device to another through a secure link.
The design must prevent a forwarded link from becoming somebody else’s access.