Release v0.20.0 - 2026-11-01

Highlights

• Akuma checks table allowlists across quoted names, qualified names, comma joins and common table expressions.
• Akuma Pro and Enterprise prompts can use their full plan allowance, including non-ASCII text.
• Akuma query throttling now tracks accounts separately.

API Changes

• Changed:
  • Nonempty guardrails.allowTables lists check every physical table reference in all Akuma query modes. Unlisted names and SQL whose references cannot be verified return a validation error.
  • Akuma prompt limits count Unicode code points. Server-added clarification context has a separate allowance, so it does not reduce the customer prompt limit.

SDK + MCP Changes

TypeScript SDK

• Clarified table-allowlist matching and supported SQL in the guardrail documentation.

Python SDK

• Clarified table-allowlist matching and supported SQL in the guardrail documentation.

Go SDK

• Clarified table-allowlist matching and supported SQL in the guardrail documentation.

MCP Server

• Updated query-tool documentation to explain table-allowlist matching and validation failures.

Breaking Changes

• Requests with a nonempty table allowlist can now return validation errors where they were previously accepted. This includes Snowflake and BigQuery queries, unsupported SQL forms, and entries that do not match canonical table names.

Migration Notes

• With a nonempty table allowlist, use the canonical spelling and qualification described in the API docs. A bare table name and a schema-qualified name are different entries.
• Nonempty table allowlists support the documented PostgreSQL and MySQL SELECT subset. Unsupported SQL or dialects are rejected. An empty or omitted allowlist leaves this check disabled.

Known Issues

• An Akuma account can receive a rate-limit response when service capacity is exhausted, even if its own query budget remains available.