Radius Pi Extensions

Pi includes the core Radius connector for signing in, loading the Radius model catalog, and making model requests. The packages below are optional additions for Radius-specific commands, tools, and skills.

After installing a package, restart Pi or run /reload. Use pi list to inspect installed resources and pi config to enable or disable individual extensions and skills.

@earendil-works/pi-radius

Install the core Radius extension package for routing controls, web search, gateway notices, and Radius API access:

pi install npm:@earendil-works/pi-radius

The package includes:

The web_search tool provides paid web research through Radius. It remains available when you select a model from another provider, but it still requires Radius authentication. Usage is billed to the organization selected during /login radius.

Radius API access

Ask Pi to inspect or manage a Radius resource and it will load the radius-api skill when needed. You can also load it explicitly with /skill:radius-api.

The skill discovers the current Radius API and can work with organization administration, members, groups, budgets, policies, analytics, Artifacts, Routing Profiles and Auto Model, Token Rewriting, and other Radius resources. It uses the Radius authentication managed by Pi.

Routing controls

With a Radius model selected, /radius opens routing status and settings for the current model and session. The status shows which upstream provider served the latest request in this session and any explicit routing override. Text commands are also available:

/radius status
/radius auto
/radius prefer <provider-id>
/radius force <provider-id>

Omit the provider ID from prefer or force to choose from the providers currently available for the model. prefer falls back when the selected provider is unavailable; force fails instead. These per-session settings do not apply to automatic models or profiles, whose routing is controlled by the organization's configuration and Auto Model policy.

@earendil-works/pi-radius-work

Install the work package for Google Workspace, image generation, and image description:

pi install npm:@earendil-works/pi-radius-work

Image generation also requires the core Radius extension package, Radius authentication, and a selected Radius model.

Google Workspace

Run /google-workspaces to connect a Google account through the browser. The extension can delegate access to Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, and Meet. Run /google-workspaces status to list connected accounts.

Tokens are stored locally by account under ~/.pi/google-workspace/tokens/. Set GOOGLE_WORKSPACE_TOKENS_DIR to use another directory. Pi shows connection status in the footer and makes the connected account email addresses available to fresh prompts so account-specific requests can select the right local connection without exposing token values.

Image tools

The image_generation tool generates a new image or edits supplied images. It writes generated image bytes to disk and returns their paths instead of adding the image data to the conversation context. It is available while the selected model uses the radius provider.

The describe_file tool sends one or more attached images to Radius and returns a text description to the active loop. It is intended for text-only models that cannot inspect an image directly and remains available when a model from another provider is selected.

Both tools require Radius authentication, and their usage is billed to the selected Radius organization.