Built in Tools

These are the native tools Jupiter registers for agents.

Tool	What it does
list_files	Explore workspace files
read_file	Read text files
search_code	Search source with ripgrep
write_file	Write file content
apply_patch	Apply structured text patches
display_image	Show images in chat
run_command	Run a shell command
task	Delegate to a configured subagent

MCP tools are added dynamically when an agent has mcp:* permission.

Permissions

An agent only sees tools allowed by its definition. Write and command capability is derived from those tool permissions.

run_command

Commands run with timeout and cancellation support. The environment starts empty; Jupiter then copies explicitly whitelisted host variables, overlays project variables, and does not automatically inherit its own sensitive credentials.

Large command output is shortened in chat while remaining available to the agent.

display_image

Agents can display PNG, JPEG, GIF, and WebP workspace images inline in chat.

Is This a Filesystem Sandbox?

No.

These tools operate on the real filesystem. Path handling normalizes workspace-relative paths, but Jupiter should not be treated as enforcing OS-level filesystem containment.

See Security Model.