Non-interactive surfaces (cron, API, ACP)
Cron jobs and other non-interactive surfaces inherit your interactive trust decision - they never prompt and never auto-trust. The project root resolves from the surface's working directory (a cron job's workdir , via the same mechanism the terminal tool uses). A cron job whose workdir is inside a repo you previously trusted loads that repo's project skills; a job in an untrusted or undecided repo loads none. In the TUI and Desktop the project root follows each session's workspace (the directory shown in the sidebar / set with the workspace picker), so starting hermes --tui inside a trusted repo registers its project skills as slash commands even when terminal.cwd is left at the default placeholder . ; two sessions open in two repos each see their own.
From the official Hermes Agent documentation.