Omni 1.1 Flash adds scene extension, 4K upscaling
Gemini Omni 1.1 now analyzes 10 seconds of prior context for seamless video extension, supports keyframe interpolation, and generates 360p previews 60% faster—available via Gemini API with production-ready controls.
Cuts iteration time for video generation workflows through faster 360p drafting and deterministic output via keyframe specification. Enables longer narrative continuity in generative video without flickering or context loss.
Replaces ad-hoc frame stitching and manual keyframe hunting. Requires Gemini API key and updates to prompt structure (`previous_interaction_id` for extensions, video references up to 3 seconds). Ready now—rolling out across Google AI Studio, Enterprise Agent Platform, and subscriber tiers.
- “the model can now analyze up to 10 seconds of prior context — a leap from previous models that only referenced the final second”
- “Generate lightweight previews in 360p resolution up to 60% faster and at a third of the cost compared to Omni 1.1's standard 720p resolution”
- “You can extend videos in 10-second increments up to a total cumulative length of 40 seconds”
- “Reference up to three seconds of video when crafting your scene”
video-generationgemini-apigenerative-mediaapi-releaseproduction-ready
Cursor joins AI SDK harness layer abstraction
Use `@ai-sdk/harness-cursor` to swap Cursor in/out of agent workflows via standardized `HarnessAgent` interface without refactoring app code.
Eliminates vendor lock-in for agentic AI: define agent logic once, test against Cursor, Claude Code, Cline, or others by changing a single import. Reduces friction when benchmarking or migrating between coding agents.
Replaces direct Cursor SDK imports with ACP-proxied adapter. Requires Node.js environment with `@ai-sdk/harness-cursor` and `@ai-sdk/harness` packages installed. Worth adopting now if you're already building with Vercel's AI SDK v7; otherwise evaluate whether the harness abstraction overhead justifies your use case.
- “The harness layer lets your application run different coding agents through the same `HarnessAgent` interface, so you can switch agents without changing your application code.”
- “Under the hood, the adapter uses `@ai-sdk/harness-acp` to connect Cursor to `HarnessAgent` through the Agent Client Protocol (ACP).”
- “Supported harnesses now include, in addition to Cursor, Claude Code, Cline, Codex, Deep Agents, Grok Build, OpenCode, and Pi, with more coming soon.”
cursorai-sdkagent-abstractionvercel Shipyard winds down IPFS maintenance September 2026
Protocol Labs defunds Shipyard; Kubo, Helia, Boxo, and public IPFS infrastructure lose dedicated maintainers—plan migration or alternatives now.
If you run IPFS nodes, use Kubo/Helia, or depend on ipfs.io/dweb.link, your tooling enters maintenance-only mode. No new features, uncertain bug-fix cadence, and public bootstrap/gateway infrastructure status unknown until Protocol Labs decides.
Replaces: Shipyard as your IPFS vendor support. Requires: immediate audit of which projects you depend on (Kubo, Helia, Boxo, IPFS Desktop, Companion, etc.) and contingency plans for ipfs.io/dweb.link services by Sept 30, 2026. Not worth waiting—start forking critical paths or switching to alternatives now if you can't self-maintain.
- “Protocol Labs has informed us that it will not be renewing Shipyard's funding”
- “Our final day of our IPFS related work will be September 30, 2026”
- “Projects maintained by Shipyard will no longer have dedicated maintainers responsible for new features, bug fixes, releases, or long-term stewardship. These include: Kubo, Helia, Boxo, Rainbow, IPFS Desktop, IPFS Companion, Someguy, Service Worker Gateway, IPFS Check, and others”
- “Shipyard will cease operating the public infrastructure it currently manages, including ipfs.io, dweb.link, check.ipfs.network, delegated-ipfs.dev, the IPFS bootstrap nodes”
ipfsinfrastructuremaintenancedeprecationdevops
GPT-5.6 Sol pricing drops 20% input, 33% output
OpenAI reduced GPT-5.6 Sol list prices with an additional 50% AI Gateway discount through September 18, making cached tokens and long-context requests proportionally cheaper.
Token costs directly affect inference budgets for production agents and streaming applications. Automatic billing on existing model IDs means no code changes required to capture savings immediately.
Drop-in replacement for existing GPT-5.6 Sol calls via `openai/gpt-5.6-sol` model ID. Requires no migration work—billing reflects new rates automatically. Worth enabling now if you're already on this model, but verify your actual usage patterns against the tiered pricing table.
- “Input drops 20%, output drops a third”
- “The discount applies on every OpenAI service tier”
- “The model ID is unchanged, so requests you already send bill at the new price automatically”
- “Rates are per million tokens for requests up to 272K tokens”
pricinggpt-5.6-solai-gatewaycost-optimizationopenai
Vercel Passport reaches general availability
Use `getIdentity()` to read authenticated visitor identity in application code after OIDC sign-in, with group claims from your provider for role-based access control.
Eliminates custom auth middleware for deployments by moving identity validation into Vercel's network layer. Developers can now enforce provider-based access control natively without managing session state or secrets in application code.
Replaces custom OAuth/OIDC integrations for deployment-level protection. Requires Enterprise plan, Vercel Connect setup with Okta/Entra ID/OIDC provider, and SDK installation (`pnpm add @vercel/passport`). Ready now—GA release with JWT verification support for downstream services and local development fallback.
- “Passport allows you to protect your Vercel deployments with your own identity provider”
- “Vercel strips client-supplied values for the `x-vercel-oidc-passport-token` header and injects the verified token after Passport validates the session”
- “The `subject` field is a stable identifier for the visitor, scoped to your team and the Vercel Connect application”
- “Vercel Passport is available on the Enterprise plan”
- “Services outside JavaScript can verify the token as a standard JWT with the published JWKS”
authoidcdeployment-protectionidentity-managementvercel