FAQ

Why can't I npm install @dsh-blue/blue?

Blue is in preview and not published to npm. The only supported install today is a local development install against a checkout — see Quickstart. v0.1.0-rc.1 will be the first released version; this site's install docs will be updated when it ships.

Pasting an image does nothing?

Ctrl-V paste depends on two things:

1. Terminal environment: a clipboard tool is probed — wl-paste then xclip on Linux (3s timeout);
2. Model capability: pasted images enter the message as image content blocks. If the current model route has no image input, messages containing image blocks are rejected — that is the upstream harness capability negotiation; switch to a vision-capable model.

Images land in the attachment store (default ~/.dsh/attachments; relocate via DSH_BLUE_ATTACHMENT_DIR or DSH_HOME), capped at 10MB per image, 8 images / 30MB / 16M pixels per message.

Why doesn't the injected AGENTS.md context show up in the transcript?

The harness injects workspace instructions (AGENTS.md and friends) and runtime-context snapshots into the session as synthetic user messages. Blue sorts by message source: human input renders as usual (❯ bubbles); synthetic messages render as nothing — no item, no placeholder — keeping the transcript clean. The content is still sent to the model in full; it is just not rendered.

Can I customize key bindings?

Not yet. Keys register through blueKeymap (duplicate bindings are rejected), but user-facing customization is deferred to a later phase (same for alt-screen surfaces). See Key bindings for everything available today.

/quit does nothing?

In the brief window before the agent attaches, /quit shows no active session instead of exiting — command dispatch checks for a current agent. Retry a moment later. Double Ctrl-C within 1 second also exits interactive mode.

When does the status-bar git badge refresh?

The git badge probes lazily through a TTL cache (branch 5s, status 15s), but the probe is session-scoped: switching branches mid-session waits until the next session switch (/new, /resume, or restart) to show the new branch.

What happens when the status bar runs out of room?

The footer has at most two rows. Entries that don't fit are dropped lowest-priority-first; over-wide entries truncate within their cluster budget. Ordering and eviction come from registry priorities (built-in entries occupy 0 / 5 / 10 / 20 / 30), not hardcoded positions.

Does bash-mode output enter the session history?

No. Commands in ! bash mode run through Blue's own executor and echo into the scroll area as shell cards — deliberately outside the session transcript, invisible to the model. Paste results back into the prompt, or let the model run a tool, when it needs to know.