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

Showing 221–240 of 471 dossiers

Bun 1.4 rewrites the runtime in Rust and moves closer to Node.js 26 compatibility

Bun 1.4 combines an implementation-language rewrite with a larger built-in standard library and a substantial Node-compatibility push. For teams already running Bun, the practical task is to validate native addons, runtime behavior and workload-specific performance rather than treating this as a drop-in minor upgrade.

Zipchat’s rebuild shows how platform risk reshaped its AI SaaS economics

Zipchat is useful as an operating case study, not a comeback story. Founder-reported figures show how a prior platform dependency failure influenced a new AI SaaS model built around reply-based pricing, channel diversification, revenue-based financing and tighter hiring discipline.

Meta Muse turns a consumer AI assistant into a persistent agent — and its first Mac zero-day tests the containment model

Muse packages persistent autonomous execution, credentials, payments, app access and memory into a mainstream consumer product. A September macOS hotfix now provides an early real-world lesson: agent containment has to protect not only the cloud runtime but also the local control path into the agent.

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.

Amazon ECS now separates control-plane failures from auxiliary-daemon failures on managed capacity

The newer `critical=false` daemon control changes ECS Managed Instances from an all-daemons-are-instance-critical model to an explicit reliability trade-off: logging, metrics or security agents can fail without forcing application workloads off the host, while ECS still emits health events and action logs.

Cursor turns cloud agents into event-driven workers — and now lets teams choose where they execute

Self-Hosted Machines changes the architecture of Cursor’s Cloud Agents more than another model option would. Teams can keep code, build outputs, secrets and terminal/browser actions on infrastructure they control, but the planning/inference loop remains a Cursor service and enterprise teams become responsible for worker images, scaling, secrets and production validation.