{
  "name": "navigating-the-terminal",
  "description": "How to explore the WebX11 terminal, find commands, check status, and navigate the filesystem",
  "tags": [
    "terminal",
    "navigation",
    "help",
    "filesystem"
  ],
  "category": "system",
  "created": "2026-07-06T00:13:29.403Z",
  "updated": "2026-07-06T00:13:29.403Z",
  "content": "---\nname: navigating-the-terminal\ndescription: How to explore the WebX11 terminal, find commands, check status, and navigate the filesystem\ntags: [terminal, navigation, help, filesystem]\ncategory: system\n---\n## Steps\n1. **Get an overview of available commands:**\n   - Type \"help\" for a full command list sorted by category\n   - Type \"status\" to see filesystem state, loaded modules, Ollama status\n   - For a specific command, use help <command>\n   - Type \"commands\" for a compact list with module source info\n   - Type \"check\" for system health including module requirements\n\n2. **Explore the filesystem:**\n   - Use ls, ll, tree to browse directories\n   - Use cd <dir> to navigate, pwd to show current path\n   - Use cat or edit to view file contents\n   - Use find or grep to search files\n   - Use du to see disk usage\n\n3. **Understand system state:**\n   - mem — memory usage (auto-shown in header on boot)\n   - status — network, files, modules, Ollama\n   - modules — module manager GUI\n   - health-check — VFS size, modules, logs, trash, skills, tool failures\n   - checkpoint-list — VFS checkpoint snapshots\n\n4. **Agent / Orchestration state:**\n   - agent-list — registered agents (type, capabilities, status)\n   - orchestrate — list active orchestrated agents\n   - lease-list — show active leases with TTL\n\n5. **When user asks a vague question:**\n   - First run status and help to understand the current state\n   - Then ask clarifying questions based on what you found"
}