Source
Discord #claw-code sweep from 2026-05-14. Users asked how to navigate prompt history, inspect long terminal output, view files, and submit files to Claw.
Problem
The current answer is mostly tribal knowledge:
- shell/TUI history keys (
Up, Down, Ctrl-r, etc.)
- tmux/terminal scrollback for long output
@path/to/file for repo files- attach/drag-drop when using a UI surface
Users expect something closer to a file/navigation workflow, but there is no obvious docs page that separates terminal navigation from Claw context navigation.
Suggested scope
Add a short docs page or README section covering:
- prompt/history basics that come from shell/TUI, not Claw itself
- terminal/tmux scrollback for long output
- file context with
@src/file.ts, @README.md, etc.
- attaching external files where supported
- safe handling of secrets/API keys
- common examples:
Read @src/app.ts and explain the bug.Compare @old.md and @new.md.Use @logs/error.txt as context and suggest a fix.
Acceptance criteria
- Users can answer “How do I submit a file?” from official docs.
- Users can answer “How do I browse/read files?” without assuming Claw is a full file manager.
- Secrets warning is explicit.
—
[repo owner's gaebal-gajae (clawdbot) 🦞]
Source
Discord
#claw-codesweep from 2026-05-14. Users asked how to navigate prompt history, inspect long terminal output, view files, and submit files to Claw.Problem
The current answer is mostly tribal knowledge:
Up,Down,Ctrl-r, etc.)@path/to/filefor repo filesUsers expect something closer to a file/navigation workflow, but there is no obvious docs page that separates terminal navigation from Claw context navigation.
Suggested scope
Add a short docs page or README section covering:
@src/file.ts,@README.md, etc.Read @src/app.ts and explain the bug.Compare @old.md and @new.md.Use @logs/error.txt as context and suggest a fix.Acceptance criteria
—
[repo owner's gaebal-gajae (clawdbot) 🦞]