AI and development — August 20, 2026

Agent platforms

Claude Platform combines action, procedure, and artifact in one production surface

Anthropic moved computer use, Skills API, and Files API to GA and added browser use, which combines page structure with screenshots. Computer use can perform several actions per model turn. Skills API stores versioned packages of instructions, scripts, and templates; Files API stores reusable input and output artifacts, up to 1 TB per organization.

The vendor offers one customer case where a workflow fell from 32 to 13 minutes, cost dropped about 30%, and completion reached 100%. It is a selected example without task count; those percentages do not transfer to other scenarios. HIPAA eligibility also does not make every application compliant automatically.

The product boundary is the more reliable fact. A tool represents action, a skill a reproducible procedure, and a file durable state between calls. An agent becomes a system when those layers stop hiding in one enormous prompt.

Source: Claude Platform GA.

Google moves Antigravity under corporate identity

Antigravity became available to some Gemini Enterprise subscribers with administrative restrictions, pooled usage, observability, and spend controls. Extensions bring the harness to VS Code and, in preview, Visual Studio, JetBrains, and Zed. The desktop app and CLI use corporate identity through WIF or ADC and regional endpoints.

"Available today" applies only to the named licenses, while several IDE integrations remain in preview. Google publishes no coding-agent quality benchmark.

The event is not about the model. In a personal tool, credentials, budget, and state usually belong to the developer. An enterprise harness must answer to the organization: who signed in, where work executes, what it costs, and which actions reach the audit trail. Antigravity becomes an enterprise product at exactly that boundary.

Source: Antigravity for enterprise.

Verifying change

An agent pull request gets an executable preview environment

LangSmith Preview Builds automatically creates an isolated production-like environment from a GitHub branch. A reviewer can test prompts, tools, traces, and failure paths before merge; each new commit produces a separate revision. Idle TTL and concurrent-preview limits constrain spend.

Public Beta is available only in LangSmith Cloud with GitHub integration. Secrets are copied from the parent at creation, so LangChain explicitly recommends separate preview credentials, especially for external contributors.

An ordinary diff is insufficient for agent code. One instruction can reshape a whole trajectory, while a new tool can expose an action invisible in prompt text. Preview turns review from reading configuration into observing behavior. It costs more than static checking, but resembles what users receive after merge.

Source: LangSmith Preview Builds.

monday.com replaces scattered AI features with a shared workspace

An Anthropic and monday.com case study describes a move from isolated summary and categorization features to an agent-first platform. Agents operate inside shared boards, context, workflows, and permissions. The companies report 5 million agent interactions in two months and more than 250,000 monday.com customers.

This is joint marketing without retention, task-success, or business-outcome baselines. Interaction count measures activity, not value.

Still, the reason for the redesign is familiar. "AI dust" adds a button to every screen but cannot follow work between screens. An agent becomes useful when it enters the same workflow and permission model as a person and can resume unfinished state rather than generate one more text.

Source: monday.com case study.

Models and inference

A small draft model accelerates a large one without changing its answer

Liquid AI released DSpark checkpoints for LFM2.5-1.2B-Instruct, 2.6B, and 8B-A1B. They perform speculative decoding: the cheap model proposes several next tokens, and the target verifies them as a batch. When accepted, output still belongs to the target model but needs fewer sequential steps.

Liquid claims up to 3.18x GPU throughput and 2.87x on-device. Maxima depend on the draft-target pair, hardware, length, and acceptance rate; speculation also uses extra memory and may not pay on short or unpredictable answers.

This is a useful systems optimization. The model is accelerated not by lower quality or a new kernel, but by dividing work between two predictors. Any meaningful benchmark must name the whole loop, not just the best multiplier.

Source: LFM2.5-DSpark.

FalconTST 2.0 enters banks as a forecasting model, not an LLM

Ant International introduced Falcon Time-Series Transformer 2.0 for cash flow, liquidity exposure, and FX management. Named integrators include Barclays, Citi, Deutsche Bank, and Standard Chartered. The company claims over 93% forecast accuracy and state of the art on MASE.

"Accuracy" without horizon, dataset, and error definition says little, and the percentage cannot be compared with MASE as though they were one metric. A previous claim of 60% savings on FX costs is absent from the day's open primary source and excluded.

The strong signal is the production task. Liquidity management needs a robust quantitative forecast inside an existing bank decision, not elegant general reasoning. A specialized foundation model competes by matching the method of verification, not by breadth.

Source: FalconTST 2.0.

Scientific agents

MAESTRO joins literature search to increasingly expensive simulation

MAESTRO builds a computational-discovery pipeline for metal-organic frameworks: it searches literature, links papers to crystal structures, assembles a computable database, and sends candidates through several simulation tiers. Promising materials for separation in humid flue gas emerged from papers about other tasks.

This is a domain-specific preprint. The abstract gives no overall success rate, cost, or expert-team comparison; "end to end" ends at computation, not an autonomous wet lab.

Its architecture is interesting in how it spends evidence. Cheap retrieval widens the funnel, structure matching makes records comparable, and expensive simulation runs only on candidates that pass. The scientific agent's value is not replacing a scientist with one answer, but preserving provenance across representations and cost levels.

Source: MAESTRO.

Market orchestration

Callosum wants to route across both models and chip types

Callosum raised a $100 million seed round for an orchestration layer that selects not only a model but an accelerator type. Investors include DCVC and the British Sovereign AI fund.

The source belongs to an investor; there is no public product demonstration or performance result. Round size does not prove the router works.

The problem itself is becoming unavoidable. A workload may run on a GPU, wafer-scale system, custom ASIC, or local device, so the backend is no longer homogeneous. A scheduler must know capability, price, availability, residency, and hardware properties. Model routing and cluster scheduling converge into one execution market.

Source: DCVC on Callosum.

The issue's main technological shift

On August 20, universality moved out of the model and into composition.

Action, skill, and artifact became separate production layers. Preview tests their joint behavior. Identity and budget cover one harness across many IDEs. A draft model accelerates a target, a specialist enters a bank workflow, and a scientific agent joins several kinds of evidence.

In such a system, replacing the model is relatively easy. Preserving procedure, state, rights, observability, and success criteria is much harder. Those layers become the real product.