Reeve
Reference & Templates

Features Reference

Comprehensive feature list and subsystem overview

Features Reference

This document provides a comprehensive overview of Reeve's features and subsystems.

Core Platform

Channels

Apps + Nodes

Tools + Automation

Runtime + Safety

Ops + Packaging

Key Subsystems

Agent to Agent (sessions_* tools)

  • Use these to coordinate work across sessions without jumping between chat surfaces.
  • sessions_list — discover active sessions (agents) and their metadata.
  • sessions_history — fetch transcript logs for a session.
  • sessions_send — message another session; optional reply‑back ping‑pong + announce step.

Details: Session tools

Skills Registry (ReeveHub)

ReeveHub is a minimal skill registry. With ReeveHub enabled, the agent can search for skills automatically and pull in new ones as needed.

ReeveHub

Chat Commands

Send these in WhatsApp/Telegram/Slack/Google Chat/Microsoft Teams/WebChat (group commands are owner-only):

  • /status — compact session status (model + tokens, cost when available)
  • /new or /reset — reset the session
  • /compact — compact session context (summary)
  • /think <level> — off|minimal|low|medium|high|xhigh
  • /verbose on|off
  • /usage off|tokens|full — per-response usage footer
  • /restart — restart the gateway (owner-only in groups)
  • /activation mention|always — group activation toggle (groups only)

Models

Subscriptions (OAuth):

Model note: while any model is supported, Anthropic Pro/Max + Opus 4.5 is recommended for long-context strength and better prompt-injection resistance.

Development Channels

  • stable: tagged releases (vYYYY.M.D or vYYYY.M.D-<patch>), npm dist-tag latest.
  • beta: prerelease tags (vYYYY.M.D-beta.N), npm dist-tag beta.
  • dev: moving head of main, npm dist-tag dev (when published).

Switch channels: reeve update --channel stable|beta|dev. Details: Development channels.

Security Model

  • Default: tools run on the host for the main session, so the agent has full access when it's just you.
  • Group/channel safety: set agents.defaults.sandbox.mode: "non-main" to run non‑main sessions inside per‑session Docker sandboxes.
  • Sandbox defaults: allowlist bash, process, read, write, edit, sessions_list, sessions_history, sessions_send, sessions_spawn; denylist browser, canvas, nodes, cron, discord, gateway.

Details: Security guide · Docker + sandboxing · Sandbox config

Remote Gateway

Run the Gateway on a Linux instance. Clients (macOS app, CLI, WebChat) connect over Tailscale Serve/Funnel or SSH tunnels, and you can pair device nodes (macOS/iOS/Android) to execute device-local actions.

  • Gateway host runs the exec tool and channel connections by default.
  • Device nodes run device-local actions (system.run, camera, screen recording, notifications) via node.invoke.

Details: Remote access · Nodes · Security

Tailscale Access

Reeve can auto-configure Tailscale Serve (tailnet-only) or Funnel (public):

  • off: no Tailscale automation (default).
  • serve: tailnet-only HTTPS via tailscale serve.
  • funnel: public HTTPS via tailscale funnel (requires password auth).

Details: Tailscale guide

macOS Permissions via Gateway Protocol

The macOS app can run in node mode and advertise capabilities over the Gateway WebSocket:

  • system.run runs a local command and returns stdout/stderr/exit code.
  • system.notify posts a user notification.
  • canvas.*, camera.*, screen.record, and location.get follow TCC permission status.

Details: Nodes · macOS app · Gateway protocol

On this page