tddworks/baguette - RepoRadar

Score8.0

Popularity1444.0

Risknone

TierGold

Score breakdown

Usefulness9.0

Novelty9.0

Momentum8.0

Maturity8.8

Open-source/build8.4

Evidence8.0

Workflow potential9.1

Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for **iOS UI test farms** — `baguette` boots simulators headlessly, streams screens at 60 fps, dispatches real touches / swipes / gestures via SimulatorKit + `IOHIDDigitizerDispatch` (no `DYLD_INSERT_LIBRARIES` dance), inspects the accessibility tree, and tail the unified log, so a CI farm can run hundreds of iOS UI tests in parallel without a Mac GUI session. Useful for **AI-agent-driven i

Who should use it

**iOS UI test farms** — `baguette` boots simulators headlessly, streams screens at 60 fps, dispatches real touches / swipes / gestures via SimulatorKit + `IOHIDDigitizerDispatch` (no `DYLD_INSERT_LIBRARIES` dance), inspects the accessibility tree, and tail the unified log, so a CI farm can run hundreds of iOS UI tests in parallel without a Mac GUI session**AI-agent-driven iOS automation** — a coding agent can drive the simulator the way it drives a browser via the accessibility tree, so Claude Code / Codex / OpenClaw can build iOS apps by actually touching the running app rather than guessing selectors**Visual regression testing** — frame captures + screencast output + the ability to composite bezel + screen + gesture overlays into one MP4 make it easy to diff frame-by-frame across commits**iOS camera pipeline testing** — `baguette` pipes a Mac webcam directly into the simulator's AVCaptureVideoPreviewLayer, AVCapturePhotoOutput, and UIImagePickerController, so an iOS app under test sees real frames; pick a camera in the browser, click Start, the iOS app sees real frames**iOS gesture testing** — `IOHIDDigitizerDispatch` fires the real iOS recognizers live so home-indicator swipes, app-switcher drags, Notification Center / Lock Screen pull-downs all behave the same way they do on a real device**Apple Watch automation** — Baguette exposes Apple Watch's digital crown + side button through the same host-HID input pipeline**AI-tool teams doing iOS app prototyping** — a coding agent that drives iOS Simulator headlessly is the right default for an iOS-side prototype loop, especially for teams that do not have a dedicated Mac with a GUI session per agentEvaluation: `git clone https://github.com/tddworks/baguette && cd baguette && swift build`, then `baguette boot --device "iPhone 16 Pro"` + `baguette stream --fps 60 --codec h264` + `baguette tap 200,400`; the README walks through the device boot paths, the streaming codec options, the gesture vocabulary, and the camera-piping setup

Who should skip it

Consider tddworks/baguette lower priority if you already have a working solution in this category.

About this signal

tddworks/baguette is tracked by RepoRadar as a apache-2.0 headless ios simulato in the tddworks/baguette is the Apache-2.0 Baguette CLI section. It was first seen on 2026-06-25 and last updated on 2026-06-25. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for tddworks/baguette are workflow potential (9.1) and practical usefulness (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.

How this item is evaluated

RepoRadar assigned tddworks/baguette a composite score of 8.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1444.0 and never affects the composite score or tier. The risk label of 'none' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.

Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.

Risk explanation

No inherent user-impacting risk is flagged from the captured evidence.

Evidence links

github.com

Closest alternatives / related signals

baguettetddworksios-simulatorheadless-iosios-automationios-26ios-26-gesturessimulatorkit