TSavo

Build or manage WOPR channels in plugins. Use when registering ChannelAdapter instances, mapping channels to sessions, or reasoning about channel metadata and context flow between channels and sessions.

Configure WOPR via CLI or daemon API. Use when reading or updating config keys (daemon, auth, discovery, plugins, or plugin data) and when you need the supported config shape.

Install, enable, disable, remove, and search WOPR plugins via CLI or daemon API. Use when managing plugin lifecycle, plugin registries, or checking installed plugin status.

Manage WOPR sessions via CLI or daemon API. Use when creating, listing, inspecting, injecting into, or deleting sessions, or when you need session conversation history or context management details.

Install, create, remove, and search WOPR skills via CLI or daemon API. Use when working with skill registries, local skill creation, or remote skill installation flows.

Flight tracking and scheduling. Track live flights in real-time by region, callsign, or airport using OpenSky Network. Search flight schedules between airports. Use for queries like "What flights are over Switzerland?" or "When do flights from Hamburg arrive in Zurich?" or "Track flight SWR123".

Control Spotify playback on macOS. Play/pause, skip tracks, control volume, play artists/albums/playlists. Use when a user asks to play music, control Spotify, change songs, or adjust Spotify volume.

Get current weather for any location using wttr.in

Installation, configuration, and deployment guide for WOPR - the self-sovereign AI session management system.

Comprehensive P2P networking plugin for WOPR using Hyperswarm, identity management, topic-based discovery, and secure peer communication

WOPR security configuration reference covering trust levels, capabilities, sandbox isolation, access patterns, and session security.

Complete WOPR CLI reference for session management, skills, plugins, providers, middleware, cron jobs, security, and sandbox isolation.

When the user asks for a code change in a TypeScript project with Sugar installed, drive the change through the sugar CLI instead of editing files directly. Sugar produces (code + tests + invariants) as content-addressed mementos with verifiable proofs, so the change ships with its proof and gates the commit on adversarial re-verification: direct edits skip that gate.