Within 10 minutes of downloading Warp, I fell in love with it.
That took me by surprise. I'd seen Warp hyped everywhere, especially among people who use Claude Code. For a long time, I resisted — partly because I have a tendency to resist hype, partly because the features felt like overkill.
Warp is a terminal replacement. It can do a lot: AI agents, coding assistants, connections to multiple model providers. If you're already using Claude Code, most of that is noise.
But there are four things about Warp that made my knowledge workflow much easier — and they're all about visibility.
1. Tabs you can actually tell apart
I had an embarrassingly simple problem: when you run multiple terminal sessions, they all look the same.
In the native Mac terminal, I'd have three or four tabs open — one for my vault, one for a project, one for git operations — and I'd constantly click the wrong one. They're just... identical white rectangles.
Warp lets you rename and color-code your tabs.
That's it. That's the feature. And it means I know where I am.
Quick reference:
- Right-click a tab to rename it
- Add colors to create visual groupings
- Example setup: "Vault" (blue), "Project" (green), "Git" (orange)
2. Pick your directory instead of typing it
Near the text input in Warp, there's a small drop-up menu. Click it, and you can select your working directory visually.
You click where you want to be. No commands, no paths from memory.
If you don't have directory structures memorized — and most knowledge workers don't — this removes friction every single time you switch contexts.
Quick reference:
- Look for the directory path near your input line
- Click to open the picker
- Select any recent or bookmarked directory
3. See your files while you work
Warp has a sidebar called Project Explorer. It shows your entire folder structure for whatever directory you're in.
When I want to say "put this in the 03-Notes folder" or "look at morning-brief-sources.md" — I don't have to remember the exact path. I don't have to run commands to check what's there. The file structure is just... visible. Right there, while I work.
I didn't expect this to matter much, but I reference file paths constantly when talking to Claude Code.
Quick reference:
- Toggle Project Explorer from the sidebar
- Click folders to expand/collapse
- Use it to reference exact file names and paths in your prompts
4. Open and edit files without leaving the terminal
This is where Warp got dangerous for me.
You can click any file in the Project Explorer and open it directly in Warp. Markdown files render properly — headers, lists, formatting all visible. Switch to raw mode, and you can edit the file right there.
I use Obsidian for my notes. I use the terminal for Claude Code. Sometimes I open Finder just to navigate to a file.
So will Warp replace Obsidian for me?
No. I still use Obsidian for focus time — when I want to deep dive into content creation without AI, just me and my notes. I also sync Kindle highlights, read-later articles, and podcast notes into Obsidian. That ecosystem is staying.
But what Warp does replace is my old workspace setup.
I used to have Terminal on one side of my screen, Obsidian on the other — constantly switching between them when working with Claude Code. Or I'd use Obsidian's integrated terminal plugin, which always felt a bit clunky.
Now when I'm doing Claude Code work, everything lives in Warp. Pop open the file explorer, check a document, close it again. Everything in one window. Cleaner.
Quick reference:
- Click a file in Project Explorer to open it
- Rendered mode: See formatted preview (markdown, etc.)
- Raw mode: Edit the file contents
- Changes save directly to the file
What I'm skipping in Warp
Warp has a lot of features I'm ignoring:
- AI agents: Warp can be a standalone coding assistant with access to multiple model providers. If you're happy with Claude Code, you don't need this.
- Paid subscription: Unless you want Warp as your primary AI coding tool, the free plan has been enough for me.
- AI credits: You get some free credits for asking the built-in AI for help with terminal commands. I haven't needed them much — the visual features solve most of my problems.
The visual layer is what hooked me — it makes the terminal less intimidating.
The gap is closing
I didn't go through a CS program. Terminals, command lines, code editors — those were someone else's tools. I started using the terminal anyway.
That's changing.
If you're a knowledge worker using Claude Code, you're already doing things that were "developer-only" a year ago. Warp is another step in that direction: a terminal that doesn't assume you have everything memorized, that shows you things instead of hiding them behind commands.
The technical gap is closing — and Warp is a small, practical example of how.
Quick reference: Warp features for Claude Code users
| Feature | What it does | Why it matters |
|---|---|---|
| Tab renaming | Name and color-code terminal tabs | Know which session is which |
| Directory picker | Visual menu to switch working directory | No terminal commands needed |
| Project Explorer | Sidebar showing full folder structure | Reference file paths while prompting Claude |
| File viewer/editor | Open, preview, and edit files in Warp | Fewer apps, less context-switching |