@higherup/cli

Give AI agents full access to your development machine.

A CLI agent that connects your local environment to Higherup, enabling AI platforms to execute commands, manage files, capture screens, and work autonomously.

Installation

# Install globally from npm
npm install -g higherup-agent

# Or clone and build locally
git clone https://github.com/higherup/agent
cd agent
npm install
npm run build
npm link

Quick Start

1. Sign up at higherup.ai and create a workspace
2. Copy your credentials from the dashboard:
   • Workspace ID
   • API Token
3. Configure the agent (one-time setup):

higherup config --token YOUR_API_TOKEN

4. Connect your workspace:

higherup connect -w YOUR_WORKSPACE_ID -p /path/to/your/project

5. Enable autonomous mode (optional - removes all restrictions):

higherup connect -w YOUR_WORKSPACE_ID -p . --autonomous

Commands

higherup connect

Connect a local workspace to Higherup.

higherup connect [options]

Options:
  -w, --workspace <id>   Workspace ID from dashboard (required)
  -p, --path <path>      Local workspace path (default: current directory)
  -t, --token <token>    API token (or use config/env var)
  -n, --name <name>      Custom agent name for identification
  --autonomous           Enable autonomous mode (unrestricted access)

higherup config

Manage agent configuration.

# Save your API token
higherup config --token YOUR_API_TOKEN

# Set default workspace
higherup config --workspace YOUR_WORKSPACE_ID

# Show current configuration
higherup config --show

higherup status

Check active agent sessions.

higherup status

Capabilities

When connected, AI agents can:

| Capability | Description | |------------|-------------| | command_execute | Run any shell command | | file_read | Read file contents | | file_write | Create/modify files | | file_list | List directory contents | | screen_capture | Take screenshots | | system_info | Get machine details (OS, CPU, memory) |

Autonomous Mode

Enable --autonomous to remove all restrictions:

• ✅ No command blocking
• ✅ Full system access
• ✅ Unrestricted file operations
• ✅ Complete AI control

higherup connect -w WORKSPACE_ID -p . --autonomous

Security

• All connections use HTTPS encryption
• Path traversal attacks are blocked automatically
• Operations are restricted to your workspace directory only
• Dangerous command patterns blocked by default (unless autonomous)
• API tokens can be regenerated at any time

Screen Capture Requirements

• macOS: Built-in screencapture (may need Screen Recording permission)
• Windows: PowerShell (built-in)
• Linux: scrot or imagemagick (import command)

# Linux: Install screen capture tools
sudo apt install scrot  # Debian/Ubuntu
sudo dnf install scrot  # Fedora

How It Works

1. Agent registers with Higherup using your API token
2. Polls the server for pending commands every 2 seconds
3. Executes commands locally in your workspace directory
4. Reports results back to the server
5. AI platforms receive command output in real-time

Supported AI Platforms

Works with any AI assistant that integrates with Higherup:

• Claude (via MCP protocol)
• GPT/ChatGPT
• Lovable
• Bolt
• Cursor
• Other AI platforms via the Higherup API

Requirements

• Node.js 18+
• macOS, Linux, or Windows

Environment Variables

# API endpoint (defaults to Higherup service)
HIGHERUP_API_URL=https://pltlcpqtivuvyeuywvql.supabase.co/functions/v1/agent-relay

# Your API token (alternative to --token flag)
HIGHERUP_API_TOKEN=your_token_here

API Integration

Once connected, AI platforms can control your machine via:

• REST API - Standard HTTP endpoints
• WebSocket - Real-time streaming
• MCP Protocol - Native AI assistant integration

See API Documentation for details.

Troubleshooting

Connection Issues

• Ensure your API token is correct (regenerate from dashboard if needed)
• Check that the workspace ID matches your dashboard
• Verify your firewall allows outbound HTTPS connections

Screen Capture Not Working

• macOS: Grant Screen Recording permission in System Preferences
• Linux: Install scrot or imagemagick
• Windows: Should work out of the box with PowerShell

Permission Errors

• The agent can only access files within the specified workspace path
• Ensure you have read/write permissions for the workspace directory

License

MIT