Shell and Agent
Run commands in the current Space and handle Agent tool requests safely.
Goal
Understand the roles of Shell and Agent, then complete one verifiable operation in the current Space.
Shell
Shell is a terminal rooted in the current Space. Use it for commands you already know.
- Open the target Space.
- Press
Cmd/Ctrl+Jto open the Shell panel. - Run
pwdand confirm that it points to the current Space. - Use
Cmd/Ctrl+Shift+Jto create a Shell tab. - Use
Cmd/Ctrl+Wto close the active Shell tab.
After switching Spaces, Shell uses the new Space's working directory and environment.
Agent
Agent is useful when a task requires project analysis, multiple steps, or tools. State the goal, scope, and completion condition in Chat:
Check Markdown links in the current Space.
Report broken links only and do not modify files.When Agent requests Shell or another tool, you can:
- Allow once: approve only the current operation.
- Allow in session: run later requests of the same kind directly in this conversation.
- Reject: keep the current state and ask Agent for another approach.
Use Ask by default. Choose Allow in session only after understanding the command, path, and impact.
Space environment variables
Project-level variables live in the current Space's .env. Open the environment editor from the Space menu. Keep credentials in dedicated variables and make sure .env is excluded from shared content and Git.
Completion check
pwdpoints to the current Space.- Agent states the tool and intended result before execution.
- You can verify the result from file changes or command output.
Common issues
- Shell asks for a directory: open a local Space first.
- Command not found: confirm that the tool is installed and check
PATH. - Agent keeps asking for approval: this is expected in Ask mode.