I built a TUI that's the perfect companion for Claude Code.
Here's the workflow I was stuck in:
1. Ask Claude: "Which files are related to the authentication flow?"
2. Claude gives me a list
3. I copy-paste file paths, open them one by one
4. Lose track of what Claude told me
5. Repeat
Claude is great at file discovery. But it doesn't help you keep context visible, integrated with your editor, and navigable.
ws solves this by becoming the output layer for Claude's understanding:
- Claude skill finds all files related to your feature
- ws saves them and displays them in a focused tree
- Press e to open any file, / to fuzzy search
- Git status inline, per-branch persistence
Now the workflow is:
1. `/ws:map authentication flow`
2. Claude finds files, automatically adds them to ws
3. Everything Claude knows about your feature is right there in your terminal
It's like giving Claude Code a dedicated UI for context. The agent discovers, ws displays.
https://github.com/n-filatov/ws
notwhalee•1h ago