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.

Secrets from 1Password, Bitwarden or Windows Credentials

In the desktop app, the composer padlock can also read a password manager of your machine. Each source found there gets its own tab next to Type and Vault:

• 1Password — through the op CLI. Install it (brew install 1password-cli on macOS, winget install AgileBits.1Password.CLI on Windows), then turn on Settings → Developer → Integrate with 1Password CLI in the 1Password app. Stib never asks for your 1Password password: 1Password itself prompts for Touch ID or Windows Hello. Pick an item, then the field to send.
• Bitwarden — through the bw CLI, Vaultwarden included (brew install bitwarden-cli, winget install Bitwarden.CLI, or the npm package). bw knows one server per configuration, so add each server in the settings below: Stib keeps a separate configuration for each. Connect a server once, with the account's personal API key (Vaultwarden: Settings › Security › Keys) or with the bw login command shown, in a terminal. In the padlock, unlock the server with its master password: it goes to bw unlock and is never stored, and the vault locks again after 10 minutes without use. Pick an item, then its field.
• Windows — the generic credentials of the Windows Credential Manager, the ones tools such as Git, Docker or Azure store there. No prompt.

The value is read only when you attach it, and leaves like a typed secret: a Secret N tile labelled with the item's name, encrypted on the card. Stib keeps no value; it remembers the item names only while the 1Password or Bitwarden session lasts. A browser has no access to these sources: copy the value from your password manager's extension into Type instead.

Settings → User → Editor & CLI → Secret sources shows each source's state, how to set it up, and lets you hide one from the padlock. Stib checks again at launch and at most every five minutes when the padlock opens; Retry checks at once.

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.