Air integrates Claude subscriptions directly without API credits or per-token billing

Air’s integration with Claude subscriptions removes a key friction point for engineers already paying for Anthropic’s services. By tying usage directly to existing Pro, Max, or Team plans, the change eliminates the need for separate API credits or per-token billing. This aligns Air’s cost structure with how users already interact with Claude, reducing administrative overhead for teams. However, the implementation’s reliance on Anthropic’s native authentication flow means Air never holds credentials, which simplifies security but creates a hard boundary for containerized workflows.

The authentication model prioritizes security and compliance over flexibility. Air delegates the entire login process to Anthropic’s documented flow, ensuring credentials remain under Anthropic’s control. This design choice addresses user concerns about third-party credential storage but introduces a limitation: isolated environments like Docker cannot access the subscription token. Engineers working in containers must fall back to API billing or JetBrains AI credits, which may reintroduce cost tracking complexities. The trade-off is clear: tighter security for the majority use case at the expense of edge-case compatibility.

The bundled Claude Agent replaces earlier workarounds like ACP, offering a first-party experience with full feature parity. Users gain access to current models, slash commands, MCP servers, and skills directly within Air, alongside improved usage reporting. This consolidation simplifies setup and ensures consistency with Anthropic’s ecosystem. However, the transition may disrupt existing workflows for users who previously configured Claude via ACP. The recommendation to switch to the bundled agent suggests Air is phasing out support for alternative setups, which could force migration for teams relying on custom integrations.

Multiproject view and improved Markdown rendering address usability gaps in Air’s interface. The multiproject view unifies task management across repositories, reducing window clutter and improving navigation between related tasks. This change reflects a shift from project-centric to task-centric workflows, which may benefit engineers juggling multiple codebases. Meanwhile, the enhanced Markdown rendering makes documentation and notes more readable without altering file syntax. These improvements are incremental but meaningful for daily use, particularly in collaborative or multirepo environments. Neither feature introduces new dependencies or costs, making them low-risk additions.