Changelog — What's New in Radius

NewIntegration

Slack agent is now generally available

Interact with Radius, draft files, and trigger codebase diagnostics without leaving Slack.

The Slack agent has moved out of beta. Every developer now has a personal operations assistant directly in Slack — no new tab, no context switch.

Ask coding and architectural questions in natural language
Trigger builds and run diagnostic scripts with a single command
Grounded answers from your codebase index (not generic AI)
@mention Radius to trigger workflows on behalf of colleagues

Mikko KiveläCPO

New

MCP interface for Claude and beyond

Every platform action is now available over MCP, so Radius slots into your preferred AI workspace.

Connect Radius to Claude web, Claude Code, Cursor, or any MCP-compatible host. Retrieve codebase files, diagnose errors, or query project files — all from your preferred AI surface.

SecurityImprovement

Folder-level permissions and audit logs

Restrict model access down to individual directories and repositories, and track token usage.

You can now control model visibility down to individual folders in your repository. Combine with role-based access to keep proprietary keys, billing info, and customer data secure.

Integration

Jira and GitHub integrations now supported

Automatically link code commits, PRs, and build test runs to Jira issues using Radius.

Link pull requests, code changes, and test results back to Jira tickets and Slack channels automatically. No more manual updates or status chasing.

Fix

Dynamic model selection bug fixed

Fixed an issue where switching models mid-chat could lose conversation context variables.

If a user changed models mid-session (e.g. GPT-4o to Claude 3.5 Sonnet), system prompts could occasionally lose context variables. Now resolved with seamless session migration.