Skip to content

v0.5.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 25 Aug 22:01
· 1 commit to main since this release
v0.5.0
ec73b91
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Installation

# Run directly
uvx climax-mcp

# Install globally
uv tool install climax-mcp

# Or with pip
pip install climax-mcp

  • Tool-call approval dialogs — Tools can declare a risk level (read, write, destructive), and CLImax shows a native confirmation dialog before running the risky ones. Uses osascript on macOS, zenity/kdialog on Linux, and a PowerShell MessageBox on Windows, falling back to a /dev/tty prompt so it survives MCP's occupied stdin. Add confirm_message for a templated prompt ("Delete {path}?"), and a resolve block to turn opaque IDs into human-readable context before asking.

  • climax --version — Prints the installed version and exits, accepted at the top level, via -V, and on every subcommand.

  • climax test-dialog — Shows a synthetic approval dialog so you can confirm your system displays one before relying on it.

  • Paginated discovery — climax_search accepts offset and returns total_matches and has_more, so agents can page through large tool sets instead of truncating.

  • Bundled gh and aws configs — 47 GitHub CLI tools and 76 AWS CLI v2 tools, risk-annotated out of the box. Reference by bare name: climax gh.

  • Supply-chain cooldown — Dependency resolution ignores distributions uploaded in the last 7 days.

  • Approval dialogs are on by default. The default policy is approval.global: write, so every tool marked risk: write or risk: destructive now prompts before running — 46 write and 6 destructive tools across the bundled configs. To restore 0.4.0 behavior, pass a policy file with approval.global: none.

  • Headless environments deny by default. With no GUI and no TTY, the default approval.headless: deny refuses the call rather than running it unprompted. If CLImax runs unattended (CI, containers, a remote MCP client with no display), write and destructive tools will now fail closed. Pass --headless-approve, or set approval.headless: approve, to auto-approve instead. This is the most likely upgrade break for existing automated setups.

  • mcp is constrained to >=1.7,<2. mcp 2.0 replaced the low-level Server decorator API with constructor-based handler registration, which CLImax cannot run against. 0.4.x installs could resolve mcp 2.0.0 and crash on startup with AttributeError: 'Server' object has no attribute 'list_tools' (#18). If you hit that, upgrading fixes it; incompatible versions now fail with an actionable error naming the required range.

See CHANGELOG.md for the full list.

Full Changelog: v0.5.0.dev2...v0.5.0

Assets 2
Loading