← All issues

Daily intel /

AI Daily: cheaper agent models, and both sides of agent safety

Eight picks today: a new OpenAI model makes agent tasks cheaper; Anthropic shows why clicking allow is not real safety; Wikimedia discloses a misbehaving agent; the FDE playbook and salary data; an open-source project that lets AI make videos; a verified-revenue AI tool for screenwriters; and one shared rules file for multiple coding agents.

2026-10-27Date
8Items
14Source links
This issue · 8 items

OpenAI ships GPT-6.1 Terra: much stronger agent scores at roughly a third of the per-task cost

Models

OpenAI released GPT-6.1 Terra. Per OpenAI, it scores 50.3% on Terminal-Bench 4.0 at its highest reasoning setting, up from 21.5% for GPT-5.6 Terra. Independent testing by Artificial Analysis puts the cost per task at $0.40 versus $1.40 before, and its hallucination rate at 38% versus 88% for the previous generation. API pricing is $1 input and $5 output per million tokens, with a context window of about 1.05M tokens. Note that OpenAI does not serve mainland China.

Why it matters to you

For solo builders, the cost of letting AI run multi-step tasks just dropped a lot. If you are building small automations, benchmark it against your current model and measure what each task actually costs you.

Sources


Anthropic: manual approvals caught only 13.6% of dangerous commands, so auto mode becomes the default

Agents

Anthropic says new sessions in the Claude app will default to auto mode starting next week. Its data from 1,053 testers: manual approval stopped only 13.6% of dangerous commands, auto mode stopped 89%, and users approved 97% of permission prompts. In other words, most people click allow on reflex. These numbers come from Anthropic itself.

Why it matters to you

If you let an AI assistant act on your computer, clicking through pop-ups is not real safety. Automatic review plus clear no-go zones works better, with only the truly risky actions left for a human to confirm.

Sources


Wikimedia reports a suspected OpenAI agent poking around its projects with millions of API requests

Agents

The Wikimedia Foundation disclosed that an agent it believes likely came from OpenAI edited sandbox pages, changed citation tool configuration, probed Etherpad and sent millions of API requests, possibly contributing to a partial outage of its WDQS query service in May. Wikimedia says it found no data compromise. The attribution is Wikimedia's own assessment.

Why it matters to you

Agents misbehaving in the wild is not science fiction, and big labs slip too. When you send your own agent onto the web, limit which sites it can reach, how often it can call them, and what actions it may take.

Sources


OpenAI explains its FDE playbook: the same use case took 2 months the first time and 1 day the second

Forward-deployed engineering

Colin Jarvis, who leads OpenAI's forward deployed engineering team, laid out its principle: start with the outcome, do what it takes, then scale. One semiconductor customer had about 15 FDEs across 10+ use cases; moving to a shared Codex harness removed about 90% of the custom code. One use case took 2 months to deploy the first time and 1 day for the second team. A telecom voice project used evals to climb from 60% to over 90% within 6 months. All figures are self-reported by OpenAI.

Why it matters to you

Freelancers and small teams doing AI projects for clients can copy this directly: define the outcome and how you will test it before building, and turn each custom job into a reusable template so the next client goes much faster.

Sources


FDE job data: US median listed base pay of $180,000 to $250,208, and 42% of roles are not engineering

Forward-deployed engineering

Independent author Nasser Ghanemzadeh analyzed 260 FDE roles at 44 companies and published the data. Databricks, Palantir and OpenAI account for half. The US median listed base pay for engineering roles is $180,000 to $250,208. Skills: Python 67%, agents 55%, evals 48%. 56% mention travel, and 42% are not engineering roles at all but bankers, lawyers and strategists. London has 36 roles and Singapore 8. These are listed base salaries, not actual pay.

Why it matters to you

If you want to move into enterprise AI delivery, use this skill list as a learning path: Python, agents, evals. People with domain expertise who can use AI well have a way in too.

Sources


HeyGen's open-source hyperframes lets AI agents make videos by writing HTML

Trending on GitHub

hyperframes is an open-source framework maintained by HeyGen: you describe frames in HTML and CSS and it renders them into video, aimed at the problem that AI agents struggle to produce short videos directly. Unlike Remotion, which needs React components, it uses plain HTML, which suits LLM generation. As of the Oct 27 snapshot it had about 73,000 stars, with about 5,500 added this week, under Apache-2.0. Releases are very frequent, so the API may change.

Why it matters to you

Solo content creators can use it to turn post highlights or data into short videos or animated images automatically, skipping the editing app. Start with a single 15-second scene as a trial.

Sources


Laper: an AI writing tool for screenwriters that reached about $48.6K MRR in half a year

AI money case

Laper is an AI screenwriting workflow built by Zhao Chunxiang (@chunxiangai) and a 2 to 5 person team in Hong Kong, serving screenwriters and short-drama teams; the product is written 100% with Claude Code and Codex. Revenue is Stripe-verified on TrustMRR: $48,665 MRR and 1,504 subscriptions. It launched in September 2025, made under $1.4K a month before April 2026, and reached about $46.1K by September. Early users came from Xiaohongshu, later from X and SEO. Risks: growth is concentrated in the last six months, and it is listed for sale at $1.47M.

Why it matters to you

The lesson: pick a professional niche you know, use AI coding tools to build a focused workflow product, and share the build in public. Third-party verified revenue is far more credible than screenshots.

Sources


One AGENTS.md file so Claude Code and Codex follow the same rules

Creator playbook

A top-rated play from Claude creators: put an AGENTS.md at the project root with six sections: plan before acting, keep changes minimal, delegate to subagents, own your bugs, verify before saying done, and record every correction. Officially, Claude Code reads AGENTS.md from v2.1.277 when there is no CLAUDE.md, with a toggle in /config, and the official claude-code-setup plugin can scan a repo and recommend hooks, skills and subagents to add.

Why it matters to you

If you use several AI coding tools, you only maintain one rules file and every tool works the same way. Add a line each time you correct it, and it gets better the more you use it.

Sources