Skip to content

docs: desktop first-run init and silent windows spawns #1016

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
edenreich merged 1 commit into from
Oct 19, 2026
Merged

docs: desktop first-run init and silent windows spawns #1016

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion desktop.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,9 @@ The app is open-source at [github.com/inference-gateway/desktop](https://github.

## How it works

On first run, the app downloads the `infer` CLI binary and installs it to `~/.infer/bin/infer`. The CLI manages the gateway server and routes requests to whatever provider you configure. The gateway binary lands at `~/.infer/bin/inference-gateway`, and config lives under `~/.infer/`.
On first run, the app downloads the `infer` CLI binary, installs it to `~/.infer/bin/infer`, and runs [`infer init`](/cli/#configuration) to seed the userspace baseline - `~/.infer/config.yaml` and the rest of the userspace config. The CLI manages the gateway server and routes requests to whatever provider you configure. The gateway binary lands at `~/.infer/bin/inference-gateway`, and config lives under `~/.infer/`.

On Windows the app spawns every child process - the CLI, the gateway, `git`, `gh`, `ffmpeg` - without a console window, so no terminal flashes while the app works. The CLI's own child processes are not covered by this yet.

Agents run through [`infer daemon`](/cli/#daemon), the CLI's hub. The app starts the daemon, connects to its AG-UI WebSocket binding as a `desktop` client, and asks it for a thread per conversation - it does not spawn a CLI process per prompt. The same daemon serves the [OpenTask browser extension](/opentask/) and the messaging channels, so all of them see one event stream, one approval contract and [one log](/cli/#the-daemon-log).

Expand Down