WaitSpin for macOS is live.
A native menu-bar companion for developers: add supported integrations (VS Code, Cursor, Devin Desktop through Open VSX, Claude Code, Antigravity CLI, GitHub Copilot CLI, MiMo Code, OpenCode, and Grok Code CLI), manage their status, and track your $.
OpenAI has announced that the Assistants API will shut down on August 26, 2026, and developers must migrate to the Responses API and Conversations API using the provided migration guide. This change affects any application currently built on the Assistants API, requiring a transition to the newer APIs to maintain functionality.
For developers, this migration impacts workflow continuity and reliability. The Responses API offers a more streamlined interaction model, while the Conversations API handles stateful multi-turn conversations. You will need to update your code to use the new endpoints and adjust request/response handling, which may affect existing integrations and testing procedures. The migration guide provides step-by-step instructions to minimize disruption.
To verify your readiness, review the migration guide and identify which of your current Assistants API calls need to be mapped to the new APIs. Test a small subset of your workflows in a development environment to ensure compatibility before the shutdown date.
Kiro IDE 1.0.395 now supports third-party extensions alongside its built-in tooling, and adopts the latest MCP protocol revision with a more reliable sign-in flow. The update also reduces extension host crashes during large agent responses and keeps agent turns active during brief network drops. This is a source-backed change to the IDE's extension and MCP integration layer.
For developers, the practical consequence is improved stability when running extensions that produce large outputs, and fewer session interruptions when connectivity is transient. The updated MCP sign-in path may require re-authenticating existing MCP servers, so verify that your configured servers still connect after upgrading. The reduced crash rate in the extension host should make long-running agent workflows more predictable.
To confirm the change in your environment, open a project with a third-party extension and trigger a large agent response, then check that the extension host remains responsive and the MCP connection stays authenticated.
Gemini Omni Flash (gemini-omni-1.1-flash) is now generally available, and the video_config now accepts a resolution parameter supporting 360p, 720p (default), 1080p, and 4k outputs. This change lets you control output resolution directly in the API, with 1080p and 4k generated via upscaling. The previous gemini-omni-flash-preview endpoint is deprecated on September 30, 2026, so plan to migrate before then.
For developers, this means you can now tailor video generation to your delivery pipelineโlower resolutions for faster previews or bandwidth-constrained clients, higher resolutions for final renders. The explicit resolution parameter removes the need for post-processing or guesswork about default output size. To verify behavior without disrupting production, run a test request with resolution set to 360p and confirm the returned video metadata matches the requested size.
GLM-5.3-Flash now supports office document and financial research workflows, autonomously breaking down goals, using tools, and refining outputs. This capability extends beyond coding, enabling the model to handle document analysis and research tasks with less manual orchestration.
For developers, this means fewer custom pipelines for multi-step document or financial tasks, as the model can self-direct tool use and iterate on results. Reliability improves through built-in refinement, but you should still validate outputs for domain-specific accuracy. A low-risk check: run a sample financial document task and compare the model's tool-selection sequence against your expected workflow.
OpenAI has announced that Cursor's direct access to its models will end on November 12, following Cursor's acquisition by SpaceX. Developers using OpenAI models within Cursor will lose that integration on that date, per the official statement.
This change directly impacts your coding workflow if you rely on Cursor's AI-assisted features powered by OpenAI. You will need to plan for a transition, as the integration will cease, potentially affecting productivity and tooling. OpenAI states it is committed to supporting affected developers, but the exact support details are not yet specified.
To verify the impact, check the OpenAI announcement link for any follow-up guidance or migration resources.
Devin's queued message handling has changed: queued messages are now delivered while Devin is in a long-running wait, and pressing Cmd/Ctrl+Enter while editing a queued message sends it immediately. This affects developers who rely on queued messages to manage long-running sessions, as the new behavior ensures that messages are not stuck until the wait ends, and the keyboard shortcut provides a faster way to send edits.
For developers, this improves workflow reliability by reducing the need to monitor sessions manually and allowing quicker intervention. The dedicated "Waiting" activity status also clarifies when Devin is intentionally sleeping, helping you understand session state at a glance. The undo toast for folder moves adds a safety net for organization changes, and the improved accessibility features make the interface more usable for reduced-motion and high-contrast users.
To verify, you can queue a message during a long-running wait and observe that it is delivered, and test the Cmd/Ctrl+Enter shortcut while editing a queued message to confirm immediate sending.
OpenAI has announced that Cursor's direct access to its models will end on November 12, following Cursor's acquisition by SpaceX. Developers using OpenAI models within Cursor will need to plan for this transition, as the integration will be discontinued on that date.
This change directly impacts workflows that rely on Cursor's AI-assisted coding features. Teams should assess their dependency on OpenAI models in Cursor and consider alternative model providers or migration paths. The transition may affect code completion, chat assistance, and other AI-driven development tasks, requiring adjustments to maintain productivity.
To verify the impact, check Cursor's official documentation or status page for any migration guidance or alternative model options. This low-risk step helps you understand the scope of the change without altering your current setup.
Anthropic's Claude Console now supports personal keys and service account keys that act as the linked account with the same permissions, and they stop working when that account is removed from an organization. This changes how you manage API credentials for automation and team workflows.
For developers, this means you can scope keys to a specific workspace or use them across admin endpoints, improving usage tracking and legitimacy control. However, be aware that key validity is tied to account lifecycle, so plan for rotation when accounts change. To verify, create a personal key in a test workspace and confirm it inherits the account's permissions without extra scoping.
Cursor Cloud Agents now let you start a project without connecting a GitHub or other SCM provider. The repo picker includes a Start from scratch option that creates an Origin repo in the background, so you can prompt the agent immediately and save work later via the Create repo button. This removes the SCM prerequisite for initial agent use, which simplifies onboarding for new projects and reduces friction when you want to prototype quickly.
For developers, this changes the initial workflow: you can iterate on an agent build before committing to a repository structure, then scaffold a private or internal Origin repo when ready. The Codebase tab lists your Origin repos for access. Note that the publish feature requires a Vercel account, so plan for that dependency if you intend to deploy directly from the agent environment. A low-risk verification step is to start a scratch project, run a simple prompt, and confirm the Origin repo appears in the Codebase tab before deciding whether to create a repo.
@RhysSullivan computer-use is unusable until it flags a takeover. polling after auth is cheaper than a prompt that waits for you to type I've signed in.
@theo /tui fullscreen is the first thing I run on a fresh checkout. the cramped Claude Code reports are still the default TUI sitting on the last 12 lines of the trace.
Antigravity CLI 1.1.22 on 27 Aug: idle tasks or subagent panels no longer redraw at ~32% CPU. They settle near 10%. A subagent timer also stopped freezing when the parent was waiting.
You still wait. The CLI just burns less CPU.
https://t.co/fDEqk35dkq
@leerob@bot The weird part is trusting compaction on a conversation you never watched. I only buy it when I can open the machine and see the files that moved.
@emollick Thinking tokens at scale are not an explanation. If I cannot point at the one decision that changed the file, the eval is just more unread output.