Find published dossiers by topic, company, product or technology.

Showing 21–40 of 107 dossiers

Railway Cloud Agents turn coding agents into persistent deployment-adjacent VMs

Railway Cloud Agents are managed, persistent development machines rather than a new model or harness. They reuse developers’ existing agent credentials, sleep when disconnected by default, retain disk state, and live inside Railway project environments—blurring the boundary between remote coding workspace and deployment platform.

Agent Plugins 1.0 now has a concrete cross-client compatibility layer for Skills and MCP

Agent Plugins 1.0 now has documented support across VS Code, Cursor, GitHub Copilot, ChatGPT/Codex, Kiro and several open-source agents. That makes the format materially more useful for cross-client distribution, but portable components remain limited to Agent Skills and MCP servers while permissions, hooks, commands and host UX stay client-specific.

Meta opens Muse Spark’s 816B weights — but large model-as-a-service operators need a separate licence

Meta Muse Spark Open is genuinely downloadable, unlike a promised future weight release. But 42B active parameters do not make its 816B weights cheap to host, and the Muse Model License is not Apache or MIT: model-as-a-service operators over $20M in affiliated annual gross revenue need a separate agreement.

Qwen3.8-27B brings stronger agentic coding into a locally deployable 27B model

The post-release evidence sharpens the original story. Qwen3.8-27B can retain useful agentic-coding performance at practical 4-bit sizes, but local model quality is not a property of the checkpoint alone: quantization, reasoning effort, context handling and the agent harness can materially change the result.

Microsoft Project Zenith turns 64GB-class Windows PCs into a standardized local-AI developer tier

Project Zenith is not a new model or another Copilot feature. It standardizes a developer-focused Windows experience and hardware floor for local AI work, with preconfigured tooling and OS settings intended to reduce setup friction and dependence on metered cloud inference.

Google is adding hard spend caps and commitment pricing for AI agent workloads

Google’s new agent FinOps model combines hard monthly spend caps that pause agent API calls, Flexible Savings Plans with one- or three-year commitments, pay-as-you-go Gemini Enterprise usage and planned deferred execution at up to half normal inference cost. The controls are useful, but commitment economics and task eligibility need to be modeled carefully.

GitSpawn shows how a repository’s own Git config can escape AI coding-agent safety boundaries

The useful lesson is architectural rather than vendor-specific: coding agents inherit execution paths from ordinary developer tooling. If an agent shells out to Git without sanitising repository-local configuration, a hidden `.git/config` can become a host-level command channel that bypasses the controls users think govern the model.

Vercel lets coding-agent harnesses use your existing subscriptions without handing tokens to the sandbox

The change separates three things that are often bundled together: the harness, the subscription that pays for it, and the sandbox that executes it. Builders can switch among supported coding agents behind one interface while reusing existing subscription access and reducing credential exposure inside agent runtimes.

GPT-6 Astra reaches broad API rollout with 1.05M context — and enterprise computer-use controls

Astra's adoption question is no longer only model capability. Builders can now model its long-context economics and task-level efficiency, while enterprises get a more explicit control plane for computer use. The same release also raises the cyber-safety boundary: OpenAI says Astra is its first model to reach the Preparedness Framework's Critical cybersecurity capability threshold.

Vercel Agent is bringing production investigations and approved actions into Slack

Vercel Agent now works in Slack as well as the Vercel dashboard, combining logs, metrics, deployments and repository context with team conversation before proposing approved actions such as pull requests, rollbacks, configuration changes and cache purges.