Use the interactive TUI

Run xcsh without --print to open the terminal user interface (TUI). Type / to discover commands available in the installed build.

How do I send prompts and local files?

Enter text at the prompt and prefix a file path with @ to attach it, as in @README.md List only the prerequisites. Autocomplete resolves the path as you type.

The same attachment syntax works when you start a session from the shell:

xcsh @README.md "List only the prerequisites"

Attach an image when the chosen model supports vision. Treat every attached file as prompt content and exclude secrets.

How do I discover controls?

Type / to list the commands the running build registered, and /hotkeys to read the active key map. Those runtime views outrank a copied key list, because extensions and releases change the available controls.

Start xcsh in the intended working directory, confirm the model indicator, and use /help before relying on a remembered shortcut. Prefix a local path only when you intend its contents to enter model context. Review every proposed tool call; pressing Enter sends the prompt, while an approved tool can write files, start processes, or call a service. Use /exit after the final response and inspect git diff or the relevant external system for actual changes.