Jerry / Docs / Installation & Setup

Installation & Setup

Jerry is delivered as a standalone desktop binary. The backend harness is completely embedded inside the app, so you do not need terminal servers or background daemons.

Installing on macOS

Jerry is available for both Apple Silicon (M1/M2/M3/M4) and Intel-based Macs running macOS 12 Monterey or later.

1

Download the Universal DMG

Download the latest Jerry.dmg from the downloads section.

2

Install to Applications

Double-click the downloaded Jerry.dmg file, then drag the Jerry icon into your Applications folder.

3

Grant System Permissions (For Computer Use)

When you launch Jerry, macOS will prompt you for two standard automation permissions if you choose to enable desktop computer control:

  • Accessibility: Enables your bots to move the cursor, click buttons, and enter text in designated tasks.
  • Screen Recording: Enables your bots to capture visual screenshots of your designated window or screen to see what they are operating.

You can verify these at any time in System Settings → Privacy & Security.

Installing on Windows

Jerry supports 64-bit editions of Windows 10 and Windows 11.

1

Run Jerry-Setup.exe

Download and run the installer. Jerry installs per-user and does not require administrative privileges.

2

SmartScreen Notice

If Windows SmartScreen displays a warning, click More info → Run anyway to complete the launch.

Installing on Linux

Jerry provides official packages for Ubuntu 22.04+ / Debian 12+, as well as a universal AppImage.

Terminal — Ubuntu / Debian Package
sudo apt install ./jerry-desktop_amd64.deb

Or for the AppImage: right-click the file, enable Allow executing file as program, and double-click to launch.

ℹ️
No Separate Server Required: When running the desktop application, all communication happens locally within the embedded client. Your bots start running immediately upon opening the app.

AI Providers & Custom APIs

Jerry operates on a transparent "Bring Your Own Key" (BYOK) architecture. You can connect your favorite cloud AI provider or run free local models on your own machine.

Configuring Cloud Providers in the App

To configure your API keys in Jerry:

  1. Click the Settings icon (gear icon) in the bottom-left corner of the sidebar.
  2. Select the Connections tab.
  3. Paste your key into the corresponding provider field and click Test Key to confirm the connection.
Provider Supported Models Where to Get Key
Anthropic Claude 3.7 Sonnet, Claude 3.5 Haiku, Claude 3 Opus Anthropic Console (console.anthropic.com)
xAI (Grok) Grok 2, Grok Vision, Grok 3 xAI Console (console.x.ai)
OpenAI-Compatible GPT-4o, o3-mini, Llama 3.3, DeepSeek-R1, Mistral OpenAI, OpenRouter, Groq, or Together AI

Using Custom OpenAI-Compatible Endpoints

Jerry has full support for any server that speaks the OpenAI Chat Completions protocol. You can point Jerry to third-party gateways, enterprise reverse proxies, or local servers:

1

Open Settings → Connections

Locate the OpenAI-compatible API key row.

2

Set the Base URL

Under OpenAI-compatible base URL, enter your custom endpoint:

  • Direct OpenAI: https://api.openai.com/v1
  • OpenRouter: https://openrouter.ai/api/v1
  • Groq Cloud: https://api.groq.com/openai/v1
  • Together AI: https://api.together.xyz/v1

Connecting to Local Offline Models (Ollama / LM Studio)

To run Jerry completely private and free of cloud fees, you can connect it directly to models running locally on your hardware:

Using Ollama

Start Ollama on your computer. In Jerry's Settings → Connections:

  • Base URL: http://127.0.0.1:11434/v1
  • API Key: Enter ollama (any non-empty placeholder value).

Using LM Studio

In LM Studio, load your desired model and click Start Server on the Local Server tab:

  • Base URL: http://127.0.0.1:1234/v1
  • API Key: Enter lm-studio.
🔒
Secure Local Storage: Keys entered in the Settings UI are stored securely in your operating system's native credential store. They are never sent to Jerry servers.

Creating & Managing Bots

In Jerry, you don't just chat with a single generic assistant. You build a specialized team of bots, each with its own role, memory, and designated working directory.

Creating a New Bot

In the Jerry sidebar, click the + New Bot button. You can configure:

  • Name & Avatar: Choose a name (e.g. Researcher, Copywriter, QA Inspector) and select an icon or upload a custom avatar.
  • Engine & Model: Pick which AI provider and model powers this specific bot. For example, use Claude 3.7 for deep reasoning and Grok for rapid search.
  • Instructions (Persona Prompt): Define how the bot should behave, its tone, format preferences, and guidelines.

Setting an Isolated Working Folder

You can bind any bot to a specific folder on your hard drive (e.g. ~/Projects/Marketing or D:\ClientWork).

When a working folder is assigned:

  • The bot can automatically read files, search contents, and write updates inside that directory.
  • The bot is sandboxed to that perimeter and cannot modify unrelated files on your system.

Long-Term Memory & Search

Bots retain conversation context across sessions. You can search past conversations and tasks using the search bar in the top navigation or ask the bot: "What did we decide about the launch date last week?"

Connected Apps & Tools

Empower your bots to take real actions across your daily tools: reading emails, triaging notifications, updating spreadsheets, and managing calendar invites.

Connecting Services

Go to Settings → Connected Apps. You can connect services with a single OAuth authorization:

App Capabilities
Gmail / Outlook Read incoming emails, summarize threads, draft reply emails for your approval.
Slack / Discord Monitor designated channels, post status updates, notify you of mentions.
Google Calendar Inspect free/busy blocks, schedule meetings, summarize daily itinerary.
GitHub / GitLab Review pull requests, read repository files, summarize new issue tickets.
Notion / Linear Create project tickets, update documents, synchronize roadmap tasks.

Per-Bot Tool Authorization

You control which tools each bot has access to. In any bot's settings panel, toggle specific integrations on or off. For example, give your Scheduler access to Calendar and Gmail, while keeping your Code Assistant scoped strictly to GitHub and local files.

Computer & Browser Control

Jerry enables bots to visually perceive your desktop and operate applications, browse websites, and fill out forms just like a human collaborator.

How Computer Control Works

When a bot receives a task requiring desktop operation (e.g. "Open the spreadsheet on my desktop, copy the Q3 numbers, and paste them into the web portal"):

  1. The bot captures a visual screenshot of your screen or active window.
  2. The model analyzes the UI coordinates of buttons, text fields, and elements.
  3. The bot dispatches precise mouse movements, clicks, and keystrokes to complete the steps.

Security & Approval Gates

Jerry puts you in full control of computer automation with two operating modes:

  • Approval Required (Default): Before performing any click, keystroke, or app opening, Jerry pauses and displays an approval card showing exactly what it intends to do. The bot proceeds only when you click Approve.
  • Full-Auto Mode: For repetitive tasks in safe environments, you can temporarily enable full-auto. You can stop or interrupt the bot at any second by pressing Esc or moving your physical mouse.
🛡️
Instant Interrupt: Jiggling your hardware mouse or pressing the emergency stop button in the Jerry window instantly revokes bot control and restores manual focus.

Scheduled Routines & Automations

Put your bots on auto-pilot. Create recurring schedules so your agents complete repetitive chores in the background.

Creating a Routine

In the Jerry navigation, select Automations → New Routine:

  • Assign Bot: Choose which bot will execute the task.
  • Task Prompt: Write the prompt (e.g. "Check my Gmail inbox for high-priority client messages, summarize them in a bullet list, and post to my Daily Briefing channel").
  • Schedule: Select frequency (Daily, Weekdays, Hourly, or custom cron expression).

Example Use Cases

  • Daily 9:00 AM Morning Briefing: Reads calendar events and unread messages to prepare a clean daily action plan.
  • Nightly Code & PR Digest: Reviews open pull requests and summarizes build test results before you wake up.
  • Competitor Website Monitor: Checks key web pages daily and alerts you if pricing or feature matrices change.

Mobile Companion Mode

Stay connected to your desktop bots while away from your desk. Review task completions and approve actions from your phone.

Download Companion Apps

The mobile companion app runs as an encrypted companion client to your desktop workstation.

iOS Companion (iPhone & iPad)

Requires iOS 17+. Native SwiftUI with Apple Passwords autofill and iOS Share Sheet integration.

Get for iOS (.IPA / TestFlight)
Android Companion (Phone & Tablet)

Requires Android 8.0+. Jetpack Compose UI with instant QR camera pairing.

Download Android (.APK)

Pairing Your Mobile Device

1

Open Settings → Companion

On your desktop Jerry app, click Settings (gear icon) → Companion and click Pair Mobile Device to generate a unique, time-sensitive pairing QR code.

2

Scan with Mobile App / Browser

Open the companion app or your phone camera and scan the QR code. The companion client negotiates a direct end-to-end encrypted connection to your desktop machine over your local Wi-Fi or private network.

Key Mobile Features

  • Remote Approvals: Receive push notifications when an agent asks for permission to execute a task, and approve with a single tap.
  • On-The-Go Chat: Message your desktop bots anytime and read updated research briefings.
  • Voice Dictation: Dictate long instructions effortlessly into your phone microphone.
  • Web Browser Fallback: If you don't have the native app installed, scanning the QR code opens a lightweight Progressive Web Companion directly in Safari or Chrome.

Privacy, Data Storage & Backups

Jerry is engineered from the ground up for strict data sovereignty. Your files and conversations stay exclusively under your ownership.

Local File Locations

All configuration files, bot memories, and conversation transcripts are stored on your local disk:

  • macOS & Linux: ~/.openmausbot/
  • Windows: %USERPROFILE%\.openmausbot\

Backing Up Your Workspace

To create a backup or migrate your bots to a new machine:

  1. Open Settings → Backups.
  2. Click Export Workspace Backup to save an encrypted archive of your bot personas, settings, and memory logs.
  3. On your new computer, click Restore Backup to reinstate your workspace in seconds.

Zero Telemetry Policy

Jerry contains no analytics beacons, tracking cookies, or prompt snooping. Network traffic occurs only between your computer and the AI endpoints you explicitly configure.

Troubleshooting & FAQs

Quick solutions to common questions and permission checks.

The bot is unable to click or move the mouse on macOS

Open System Settings → Privacy & Security → Accessibility. Ensure Jerry is toggled ON. If it is already ON, toggle it OFF and back ON once to refresh macOS permission tokens. Do the same under Screen Recording.

"Connection Refused" when using Ollama or LM Studio

Ensure your local server is actively running in the background before sending messages in Jerry:

  • For Ollama: Open your terminal and run ollama serve or ensure the Ollama menu bar icon is active. Test in your browser at http://127.0.0.1:11434.
  • For LM Studio: Ensure the green "Start Server" toggle is active on port 1234.

How do I reset a bot's memory if it gets stuck?

Inside the bot chat window, click the menu dots in the top right corner and select Clear Active Turn or New Thread. This resets the immediate context window while preserving the bot's base instructions.