Desktop Features
The desktop app renders the same workspace as the web client and adds native operating-system actions.
Editor and terminal integration
Choose defaults in Settings → User → Editor & CLI. Stib detects supported applications on the client machine and lets you select a custom executable when detection is insufficient.
From project, Git, diff, and file actions you can:
- open a repository or file in the preferred editor;
- open a terminal in a project or worktree;
- reveal downloaded files or desktop logs;
- download one attachment or a ZIP of several attachments.
The server path must also make sense on the client for local open actions. In a remote-server deployment, use a shared mount or remote-development editor setup; Stib does not transfer an entire repository for this action.
Windows and conversations
Open a conversation in a separate native window to keep it visible beside the board. Stib synchronizes the same server-side card; typing in two windows does not create independent conversations.
The desktop app can also open additional Stib windows. Each connects to the configured server and shares the signed-in account state.
Preview window
The native preview tool can open a project URL in a dedicated window and provides:
- desktop, tablet, and phone viewport sizes;
- manual resize and toolbar-height control;
- developer-tools toggle;
- navigation and runtime-error reporting;
- console and performance feedback;
- component/element selection callbacks;
- page-stability checks and JavaScript evaluation;
- screenshot capture attached to the Stib workflow.
Only preview URLs you trust. A preview is live application content, not a static image or security sandbox.
Native theme and updates
The client can follow the operating-system light/dark theme while still applying user appearance settings. Signed in-app desktop updates follow the selected stable/beta channel on macOS and Windows and are independent from server updates. Linux uses replacement DEB/RPM packages.
Desktop diagnostics
Use the desktop log export when the native shell, updater, preview, downloads, editor opening, or window management fails. Use server logs for agent, API, database, integration, or repository failures. A single incident can require both.
Next: Desktop Installation, Settings, and Git Integration.