uttrflow / uttrflow/uttrflow-swift
uttrflow-dev probe surface has never been run, so the inline-suggestion capability table is empty
- Dominant language
- Swift
- Stars
- 4
- Forks
- 17
- Avg merge
- 3h 32m
- Merged PRs (30d)
- 277
Description
Tab-to-complete draws its suggestion inline, in the field you are typing in, and that only
works in applications whose text fields answer the Accessibility questions the app asks. How
many applications those are has never been measured, so the capability table in
`Docs/predict-probe.md` is empty and the decision it exists to settle is unmade.
## Where it is
`Docs/predict-probe.md:76-89`:
> `uttrflow-dev probe surface --seconds 120 --output Docs/predict-sweep.md`
>
> **Not yet run.** Accessibility is granted per binary, and `uttrflow-dev` does not have it.
The probe itself is `Sources/uttrflow-dev/Probe.swift:17` (`probe surface`). It reports, per
field: whether the inline ghost can be drawn, whether only a floating suggestion is
possible, and whether nothing is. `CapabilitySweep` aggregates the readings and answers the
question the phase exists for — below 30% reach, leading with the inline ghost is the wrong
choice, and there is no fallback surface.
`Docs/predict-sweep.md` is the output file and does not exist yet.
## What to change
Run it on your own Mac and contribute the table.
```
swift build -c release --product uttrflow-dev
```
Grant `.build/release/uttrflow-dev` Accessibility in System Settings › Privacy & Security ›
Accessibility, then:
```
.build/release/uttrflow-dev probe surface --seconds 120 --output Docs/predict-sweep.md
```
While it runs, click into a text field in as many of these as you have: Terminal, Chrome,
Safari, Slack, Mail, Notes, Word, Cursor, VS Code, Xcode, Messages, Finder, Music, Preview,
Numbers, Pages, Linear, Notion, Figma, System Settings. The probe prints each new field as it
sees it, so you can watch it working. Fields are told apart by application, role and
identifier, so a browser's address bar and a search box on a page stay separate rows.
Open a pull request with `Docs/predict-sweep.md` and a line saying which macOS version and
which Mac it was taken on. A partial sweep is worth having — say which applications you
covered.
## Notes
- The probe reads only whether a field answers, and what kind of field it is. It does not
read what you typed. Please skim the file before you push it anyway, and drop any row that
names something private.
- `uttrflow-dev probe tap --seconds 20` (`Docs/predict-probe.md:100-107`) is unrun for the
same reason and is a separate, smaller contribution if you would rather do that one.
Contributor guide
Research direction
Read Docs/predict-probe.md:76-89 and Sources/uttrflow-dev/Probe.swift:17, then build the release uttrflow-dev product. Grant Accessibility permission and run probe surface for 120 seconds while visiting the listed macOS applications. Done means adding Docs/predict-sweep.md, noting the macOS version and Mac used, and identifying any applications covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, swift
- Domain
- accessibility, desktop, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100