CLIO Documentation / Tools Reference

Tools Reference

Complete guide to CLIO's built-in tools

CLIO provides a comprehensive set of tools for interacting with your system. Each tool is operation-based with multiple capabilities.

file_operations

Purpose: File and directory management

Operations:

version_control

Purpose: Git version control operations

Operations:

terminal_operations

Purpose: Execute shell commands safely with validation and timeout

Operations:

Commands are classified by intent (network access, credential reading, system destruction) and confirmed with the user based on risk level.

memory_operations

Purpose: Store and recall information across sessions

Session Memory:

Long-Term Memory (LTM):

todo_operations

Purpose: Manage structured task lists with progress tracking

Operations:

web_operations

Purpose: Fetch URLs and search the web

Operations:

code_intelligence

Purpose: Code analysis, symbol search, and project history

Operations:

user_collaboration

Purpose: Request user input during tasks

Operations:

This tool implements checkpoint discipline - the AI pauses execution and waits for human input before proceeding. It's free (doesn't consume an API request) and blocks until the user responds.

apply_patch

Purpose: Apply diff-based patches to create, modify, or delete files

Uses a lightweight diff format that's more efficient than full file rewrites. Each patch can contain multiple file operations with context-based anchoring for precise edits.

Supported operations within a patch:

remote_execution

Purpose: Execute CLIO tasks on remote systems via SSH

Operations:

Copies the local CLIO installation to remote systems via rsync, ensuring version consistency. API keys are passed via environment variables and never persisted on remote systems.

agent_operations

Purpose: Spawn and manage sub-agents for parallel work

Operations:

Sub-agents run as separate processes and communicate with the parent agent via a message-passing system. The parent acts as a manager - spawning tasks, monitoring progress, and validating results.

Tool Transparency

When CLIO uses tools, you see real-time notifications showing what's happening:

SYSTEM: [file_operations] - Reading ./config.json (254 lines)
SYSTEM: [version_control] - git status
SYSTEM: [terminal_operations] - Executing: npm install

All tool calls are visible, so you always know what CLIO is doing on your system.

Next Steps