Documentation
Writing an otty.toml
One file per app, reviewed like code. The references below are the whole format; the JSON schema checks it.
The top of every otty.toml: id, name, executables, platforms, and where a package installs its own copy.
The [commands] section: fields, tasks and groups for a form, and how they become completion candidates.
The [dotfiles] section: paths, credential files, secret fields and machine-local lines.
Working through a list rather than adding one tool you happen to use.
otty-toml v1, the same file CI validates every manifest against.
How to add an app, and what review looks for.
Privacy
This site does not inspect executables, shell state, local paths or form values. Form examples are static; there are no execute, upload or AI endpoints.
API
GET /api/v1/apps lists metadata and takes q, has (gui, autocomplete, dotfiles), platform and limit. GET /api/v1/apps/{id} selects immutable revisions. Fetch the returned URL and verify sha256 and byte_length before caching. CORS is public and carries no cookies.