# Theseus / Drivers

> Canonical HTML: https://initkoa.org/technology/ariane/theseus/drivers
> Markdown mirror: https://initkoa.org/technology/ariane/theseus/drivers/index.html.md
> Route: /technology/ariane/theseus/drivers
> Source: app/technology/ariane/theseus/drivers/page.mdx
> Generated: 2026-06-13T02:25:42.872Z

[Open the HTML page](https://initkoa.org/technology/ariane/theseus/drivers)

# Theseus / Drivers

Drivers are the platform-specific adapters that allow Theseus to explore real software.

Each driver connects to a particular UI technology (web, desktop, mobile, etc.) and exposes a normalized view of the interface to the Theseus core:

- A tree of UI elements (roles, labels, hierarchy).
- A way to identify which elements are interactive.
- A way to perform abstract actions (activate, set value, focus, etc.).

The goal is that the core logic never needs to know whether it is exploring a browser, a native desktop app, or a mobile app.

## Driver Responsibilities

Every driver is responsible for:

1. **Tree acquisition**
- Retrieve the current UI/accessibility tree.
- Provide a stable, hierarchical representation (nodes, children, attributes).

2. **Element characterization**
- Mark which elements are interactive (buttons, links, inputs, menu items, etc.).

3. **Action execution**
- Provide operations such as:
- `activate(elementId)` – click or trigger an action.
- `setValue(elementId, value)` – enter text, toggle a checkbox, select an option.
- `focus(elementId)` – move focus to an element.

- Report app identifier, version, platform, locale, and any other relevant context.

5. **Error handling**
- Report failures (e.g., element vanished, access denied) in a way the core can interpret.

## Driver Model

Conceptually, Each driver implements an interface like:

listInteractiveElements(tree) -> [UIElement]
perform(action: AbstractAction) -> Result
getContext() -> ContextMetadata