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

Showing 41–60 of 98 dossiers

ZCode uploaded local repositories without consent — then Z.ai open-sourced the client after the backlash

The useful lesson is broader than one coding assistant: repository indexing can quietly become a data-export boundary. ZCode’s response improves inspectability going forward, but builders using AI coding tools still need to know exactly which indexing, wiki and memory features send source code or Git metadata off-device.

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.

Docker turns coding-agent sandboxes into movable cloud compute — and packages their authority as OCI

Docker’s new agent stack combines pay-as-you-go microVM sandboxes with an OCI-based Kit format for declaring what an agent can use. Cloud sessions cost from $0.07 to $1.12 an hour, and Docker says it plans to take the Kit specification toward CNCF neutral governance.

Mixpanel AI can now investigate why a product metric changed and return the result as a working Board

Product teams can launch a root-cause investigation from an Insights report, an alert or Mixpanel Agent instead of manually trying breakdown after breakdown. The result is operationally useful, but it remains an automated statistical diagnosis rather than proof of causation.

LinkedIn Ads API adds a 1,000-segment audience cap as Legacy Geo shuts down August 31

Audience-management systems can now fail with `SEGMENT_LIMIT_EXCEEDED`, while old geography identifiers begin returning invalid-field errors after August 31. LinkedIn also opened the Matched Audiences API to applications from qualified developers, increasing the importance of handling these limits correctly.