github craft-ai-agents/craft-agents-oss v0.15.10

one hour ago

Bug Fixes

  • Pi sessions on an OpenAI API key answer again — With Rich tool descriptions on (the default), a new Pi session on an OpenAI API key failed its first message with "Invalid schema for function 'read': … 'additionalProperties' is required to be supplied and to be false". Craft adds its intent and display-name fields to each tool and also removed additionalProperties: false from the tool's schema, which OpenAI requires on the strict tools Pi sends. The schema now keeps it, on both the Responses and Chat Completions APIs. Fixes #1134. Thanks to @67-luck for the original PR (#1135).

  • Each Claude connection uses its own account — With two or more Claude subscription connections, every session used the account that had signed in or refreshed last, whichever connection you picked. Each connection now uses and refreshes only its own sign-in, and a failed refresh on one account no longer signs out the others. Sessions on different Claude connections (subscriptions, API keys or gateways) also stay on their own when used side by side, and so does the summary written when a session continues in a new one or moves to another workspace: a session's Claude process started with the credentials and endpoint of whichever session had been set up last. Claude settings exported in your shell, such as ANTHROPIC_AUTH_TOKEN or CLAUDE_CODE_USE_VERTEX, no longer take over from the connection either. Testing a connection in Settings → AI also uses only the credentials being tested: after a session on a gateway, testing a plain Anthropic API key could send the key to that gateway. A connection still holding another account's sign-in asks you to sign in again at its next token refresh. Craft can tell only for connections that show their account email in Settings → AI, so if you use several accounts, sign in again on any that don't. Related to #1129. Thanks to @KostiantynBk for the original PR (#1081).

  • An expired Claude sign-in is cleared — Once a Claude subscription's refresh token expired, Craft kept it: every new session tried to refresh it again and showed "Failed to get OAuth token", and the connection still looked signed in, so nothing asked you to sign in again. Craft now clears the sign-in whenever Anthropic says its refresh token is invalid, expired or revoked, and Settings → AI shows the connection as signed out. Network errors, rate limits and server errors still keep it. Fixes #1129. Thanks to @67-luck for the original PR (#1136).

  • Claude sessions no longer fall back to another login — When a Claude connection's credentials couldn't be loaded (an expired sign-in, a missing API key, no connection at all), the session still ran, and the Claude CLI signed in with whatever login it found, such as your own Claude Code account. The message now stops with an error card instead: Session Expired, whose Re-authenticate button now opens Settings → AI (it did nothing before), or Invalid API Key. When refreshing the sign-in failed only for the moment (offline, a server error), or Craft couldn't read its stored credentials, the card offers Retry instead of asking you to sign in again. Related to #1129.

  • Sending a message no longer freezes the app in a large git repository — To list the project's CLAUDE.md and AGENTS.md files for the agent, Craft searched the whole git repository around the working folder. In a large one (a home folder under git, for example) that froze the app for 30–40 seconds when you sent a message, up to once every five minutes, and with many such files elsewhere in the repository it listed unrelated ones instead of the working folder's own. Craft now reads only the folders from the repository root down to the working folder, and the working folder's subfolders: at most 6 levels, 4,000 folders or 150 ms, skipping hidden, dependency and build folders. Fixes #1140. Thanks to @67-luck for the original PR (#1141).

Don't miss a new craft-agents-oss release

NewReleases is sending notifications on new releases.