The desktop app is where most people will use Pioneer. It is a native app, not a web shell. You use it to connect gateways, work in the default workspace, talk to models, inspect tool runs, configure providers, manage skills and MCP servers, and keep an eye on tasks. The important thing to remember is that the desktop app is a client. It gives you control, but the gateway owns the work. Provider calls, tool execution, task runs, skills, MCP servers, and stored Pioneer state belong to the gateway you are connected to.Documentation Index
Fetch the complete documentation index at: https://docs.getpioneer.dev/llms.txt
Use this file to discover all available pages before exploring further.
Local Use
For a single-machine setup, the desktop app can start and manage a local gateway. This is the easiest way to try Pioneer: install the app, start the local gateway when prompted, add a model provider, and create a thread. In this setup, tool calls happen on your computer. If an agent lists files, it lists files visible to your local gateway. If it runs a shell command, it runs on your machine as the gateway user.Multiple Gateways
One desktop app can connect to any number of gateways. This is useful when your environments should stay separate. You might keep a local gateway for everyday experiments, a work gateway close to work repositories and accounts, a home server for long-running personal tasks, and a sandbox gateway for testing risky skills or MCP servers. Switching gateways is more than changing a label in the sidebar. You are switching execution environments. A thread onWork uses work provider keys and work tools. A thread on Home Server uses the server’s files, network, and services.
What You Do In The App
Most daily work happens in three places. The gateway switcher tells you which environment you are using. Check it before running tool-heavy prompts. The current workspace is created automatically on first launch. For now, use threads to keep context clean inside that workspace, and use separate gateways when environments need to be separated. Threads are where conversations happen. The thread timeline shows messages, model output, tool calls, tool results, errors, retries, and final responses. When an agent changes something or a tool fails, the timeline is the first place to inspect.Settings
Settings are split between app-level preferences and gateway-owned configuration. Provider credentials, skills, MCP servers, and tasks belong to the gateway. If you connect to another gateway, configure them again there. That separation is intentional. It lets one desktop app control several independent Pioneer environments without mixing their state. Gateway bearer tokens saved by the desktop app are stored in the desktop keystore. The gateway registry keeps onlyauth_token_ref values, so raw bearer tokens are not serialized into gateway-registry.toml.
Localization
The desktop UI includes English, German, Spanish, French, Hindi, Japanese, Russian, and Chinese locales.Workspace
Understand the default workspace and organize work with gateways and threads.
Threads
Read timelines, tool events, and conversation history.