Teach vs Microsoft Skill Recorder
Shipped 2026-10-24: all 7 items are merged and deployed (platform #1846 #1847, allternit-ai #812).
Who builds what
| Worker | Repo · branch | Builds |
|---|---|---|
| A | platform · feat/teach-v2-api | /api/har-derived-api/teach/distill (redact, then model writes goal + steps + inputs; rules fallback), saved Teach skills (server, per user), Teach docs |
| B | platform · feat/teach-v2-desktop | Desktop recorder: URLs, clicks in Allternit's browser, app switches, screenshots kept on device, mic narration (local STT), ⌘⇧R, floating record bar |
| C | allternit-ai · feat/teach-v2-ui | Review (privacy check) → Analyze → Editor (steps, inputs, timeline) → Save skill (SKILL.md), Run on a schedule, Replay; desktop + phone layouts |
The flow
Limits to know
- Desktop records clicks only inside Allternit's own browser. Other apps show up as app switches plus screenshots, and the screenshots never leave the device.
- On web, the extension and the phone, recording is network traffic (HAR) or an import, plus a typed note. Narration and ⌘⇧R work on Desktop only (⌘⇧R is the browser's hard reload).
- A schedule needs a bot, because routines run in a bot's chat.
Where it is live
| Surface | State |
|---|---|
| ai.allternit.com | live at 713e00a |
| m.allternit.com PWA | deployed 6ad7c09f |
| Desktop runtime | r20261024.1826-ed6a53f, darwin and linux |
| Your Desktop | build 6301 installed; ⌘⇧R registered |
| Docs | Teach guide deployed |
| Mail-host API | GitHub deploy on ed6a53f running (about 70 min of tests) |
Also fixed: starting a recording (and signing in through the OAuth popup) used to wipe Desktop's API routing, auth headers and CSP until a restart.
Other people's Desktop apps get the record bar and ⌘⇧R in the next public app release. The runtime already gives them the new Teach screens and API.