Add a File explorer chip to the native Warp agent input toolbelt (parity with CLI agent toolbelt)

[behinddwalls]

Summary

When a third-party CLI agent (Claude Code, Codex, etc.) is running in a pane, Warp attaches the CLI agent toolbelt, which includes a File explorer chip right next to the input. Warp's own agent input has no equivalent — there is no File explorer chip and no way to add one.

Current behavior

Third-party CLI agent input — toolbelt includes File explorer and Rich Input ^G chips, and the layout is customizable via right-click → Edit CLI agent toolbelt, or Settings → Agents → Third party CLI agents → Toolbar layout.

Native Warp agent input — the toolbelt has the working directory, branch, diff count, PR chip, model picker, voice, and image upload. No File explorer chip, and no toolbelt layout editor at all.

To browse files while using the native agent, you have to leave the input: CMD + \ to open the left panel and switch to the File Tree tab (or bind a custom shortcut for it in Settings → Keyboard shortcuts).

Proposed behavior

Add a File explorer chip to the native Warp agent input toolbelt, ideally with the same customization affordances the CLI agent toolbelt already has (reorder, hide, move between left/right sides).

Failing that, a toolbelt layout editor for the native input — parity with Edit CLI agent toolbelt — would let people opt into it themselves.

Why

It's a surprising asymmetry: the feature exists, works well, and is one click away in the CLI agent case, but is unreachable from the input when using Warp's own agent. @ mentions cover referencing a known path, but not browsing to discover one, which is exactly what the File explorer chip is for.

[oz-for-oss]

@behinddwalls

Here's what I found while triaging this issue:

Thanks for the detailed parity request. This looks like an actionable native-agent/toolbelt feature gap: File Explorer is available in the third-party CLI agent toolbar, but it is not currently available as a native Warp agent input chip.

Maintainer details

I concluded that feature request to add File Explorer chip/toolbelt parity to the native Warp agent input..

Triage summary

This is an actionable feature-parity request for the native Warp agent input/toolbelt rather than a bug. The report asks for the File Explorer chip that exists in third-party CLI agent toolbars to also be available from the native Warp agent input, ideally through the same toolbar customization affordances.

Code findings

• AgentToolbarItemKind::FileExplorer exists, has the expected label/icon, and is included in the CLI agent defaults and CLI configurator availability.
• FileExplorer is currently marked CLIAgentOnly in AgentToolbarItemKind::available_in, and AgentToolbarItemKind::all_available() for native agent view does not include it.
• Native agent footer rendering filters out items that are not available for agent view, so even a saved/custom native toolbar layout cannot render FileExplorer today.
• The existing toolbar editor infrastructure has separate AgentView and CLIAgent modes, so the likely implementation path is to product/design-confirm whether File Explorer should be default or opt-in for native agent, then make the item available/renderable in the AgentView path and wire the click behavior to the existing project/file explorer action.

Duplicate check

I checked open issues across the repository and targeted searches for File Explorer, agent toolbar/toolbelt, native agent, CLI agent, and chip-related wording. I found related file tree and agent toolbar requests, but not two or more existing open issues that request this exact native-agent File Explorer chip parity.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz