1. Agent
The agent states the goal: type a character, complete a field, or invoke a command. It should not assume that the rendered character tells it which physical key to send.
From text to physical keystrokes for AI agents
Convert more than 1,000 Unicode characters into deterministic AZERTY Global sequences ready to adapt to your automation driver.
From intent to application
Robust keyboard automation keeps intent separate from the mechanics of the system that executes it.
2. Logical sequence
The specification describes physical positions and logical modifiers in a portable order. This layer is auditable, testable, and independent from the driver you select.
3. Driver, then application
The driver translates the logical sequence for the operating system or hardware. The application then receives events; the installed and active layout determines the resulting text.
When to use this converter
Use it when a workflow must reproduce real typing on a machine configured with AZERTY Global: a computer-use agent, interface QA, an RPA robot, a demonstration station, robotics, or a KVM-controlled machine. In all of these cases, the final text depends both on the active layout and on the driver injecting the events.
Do not use it as a substitute for a text field, business API, clipboard, or semantic text-entry mechanism your tool already supports. Keystroke automation is appropriate when keyboard behaviour itself is what you are testing or controlling; otherwise, direct text entry is simpler and less brittle.
The key model
The contract uses KeyboardEvent.code: it identifies a physical position such as KeyA or Digit2, rather than deriving a key from the rendered character. Logical modifiers are explicit, including AltGr, and one sequence can contain several ordered steps.
Dead keys need particular care. They produce an intermediate state, then compose with the following key. The converter therefore keeps the complete sequence order instead of reducing an intent to a single character. That matters for accents, symbols, and languages that rely on composition.
The output is never universally executable: Windows, macOS, Linux, browsers, remote sessions, accessibility permissions, and hardware drivers do not expose identical injection capabilities. Always confirm the target OS, the installed layout, and the currently active layout before running a critical workflow.
Specification v0.1
The versioned files are the reference for implementing or validating a driver. The dataset defines AZERTY Global sequences; the schema lets you validate objects emitted by your automation chain.