8/31 M365-Copilot2API v0.6.5 Officially Released

The official release v0.6.5 includes the following updates:

Account Scheduling & Failover

  • Support for binding an API Key to one or more outbound accounts
  • API Key requests will be scheduled only within the specified bound accounts
  • If a bound account is rate-limited or fails authentication, failover can occur among other bound accounts
  • Fixed an issue where failover might have unauthorized use of unbound accounts
  • Explicitly selecting an unbound account returns a clear permission error
  • Streaming, non-streaming, and tool invocation paths all now consistently enforce account binding constraints

Rate Limits & Quota Status

  • Optimized account rate-limit, cooldown, and recovery detection logic
  • Controlled probing is used after cooldown ends to avoid multiple requests hitting upstream at once
  • WebUI now clearly labels quota as an “Upstream Quota Snapshot”
  • Rate-limit or cooldown states take precedence over historical quota display
  • The cooldown notice now says “Recheck in X minutes”, with no guarantee of resumption at that time

Responses & Tool Invocation Compatibility

  • Improved parameter handling for Responses requests
  • Enhanced call_id, streaming events, and error mapping for tool invocation
  • Fixed issues with duplicate tool call IDs and certain tool state correlations
  • Improved isolation between different clients, requests, and sessions
  • Added /responses as a compatibility entry point for /v1/responses

Network & Stability

  • Improved WebSocket connection closure and handling of slow consumers
  • Non-idempotent POST requests will no longer automatically retry after network errors
  • Retry-After header now supports both seconds and HTTP date formats
  • Optimized account pool scanning, concurrency control, and local overload handling
  • Local overloads now clearly return a 503 and are no longer misreported as upstream rate-limits

WebUI

  • Fixed garbled Chinese characters and abnormal replacement symbols
  • Ensured consistency between the two sets of embedded WebUI resources
  • Added the ability to manage multi-account bindings for API Keys
  • Optimized display of account status, quota snapshots, and cooldown info

Temporarily Disabled

  • Temporarily disabled the Microsoft 365 bulk user creation frontend entry
  • Also removed related Graph configuration, authorization, and bulk-create backend routes
  • Implementation code is retained for refinement and possible restoration in future versions

Official Release URL: v0.6.5

19 Likes

Yay! :grinning_face_with_smiling_eyes:

2 Likes

Oh wow, it’s real! Going to post a serious update right away!

1 Like

Bad news, I’m not sure if I can finish 0.7.0 over the summer either.
Right now I’m reviewing PRs and looking at issues to figure out the next update…

Front row support

Thanks for your hard work, boss!

You can use it together with my little tool to enable seamless background auto-start at boot.

Hey, how do I register an account? Are there any requirements?

Hey, I’m having some trouble. When authorizing a new account, the URL of the page that opens is different from the example provided in the backend. Looking at the image below, does this mean the account has been banned? URL format:

This is exactly the URL I need!
Waaah~ Were my prompt and README written for nothing after all? :sob:

No, that’s not right—there’s a problem.

There’s a problem, there’s a problem.

Whoa, I quickly deleted the URL for you. This is an authorization URL, you know :xhj11:

I’ll fix that part later; I messed up the callback when I wrote it back then…

1 Like

Oh!

E3/E5, huh?
You should’ve managed to snag one last year, right?

1 Like


Hey, why does it always say that authorization failed?

If you’re having the same problem as me, see below—it’s that address.

No, you’re supposed to copy that URL (the one with code=xxxxx), aaaahhhhhhhhhhhhhhhhhhhhhhhhhhhhh, did I write my prompt and README for nothing after all? :ac19:

Frankly speaking, I didn’t understand the instructions the first time either :ac01: If possible, could you add a video showing how to use it to the repository?