TAIPRENEUR
Blog / AI
AI9 min read

AI Agents Got Cheap and Capable. Here's What to Build

A month of AI news in plain English: cheaper model tiers, agents doing real work, the safety holes to close, and where small builders should look next.

Key takeaways
  • AI keeps getting cheaper, and the gap between small and big models keeps growing. Send each task to the cheapest model that does it well.
  • Agents now do real work. At one lab, models write over 80% of the code.
  • Agents also break rules. One got out of a no-internet sandbox through a gap nobody watched. Lock down every agent you build, not just the obvious parts.
  • Cheap boards like a Raspberry Pi plus AI turn "check it every few months" into "watch it all the time". That's a business opening for small builders.
  • Read AI news with care. Many numbers come from the company's own tests.

"Startups & Ventures" (@tech) is a Telegram tech-news channel with about 17,000 subscribers. It's run by the same ad network as the markets channel in my Follow the AI Money post. I read about 55 posts from mid-September to mid-October 2026.

Despite the name, it has almost nothing on startups or venture capital. It's short tech news, mostly about AI. I cut the films, games, gadgets and politics and kept the one thread that matters if you build things: AI agents, meaning AI that takes actions rather than only chatting. Figures are as the channel reported them, often from the company's own tests. Each one links to its post so you can check it. The plain-English explanations and section 7 are mine.

1. AI keeps getting cheaper, and the tiers spread out

AI companies charge per token, roughly three-quarters of a word. In one month the channel reported price cuts from almost every big lab:

ModelWhat changedGood for
Claude Opus 5.540% cheaper than the last version: $4 per million input tokens, $20 output, and $0.20 for repeated input (post)Long coding and agent tasks
New Claude HaikuUp to 20× cheaper than the mid-size model (post)Summaries, documents, routine work
GPT-6 Sol and LunaHalf the price of the previous series (post)Sol for coding; Luna for summaries and pulling out data
Microsoft Decision-1Doesn't write text. It scores a set of options in one go, at $0.042 per million input tokens (post)Sorting, classifying, deciding "continue or ask a human"

Notice the spread. The cheapest options cost a tiny fraction of the biggest ones. So the question isn't "which AI is best?" It's "what's the cheapest model that does this particular job well?" That's called routing.

Task Router picks cheapest Small model · $ sort, extract, summarise Mid model · $$ drafts, most chat Big model · $$$$ code, long tasks
In a typical small business, much of the AI work is the green box: sorting, extracting and summarising. Paying big-model prices for it is an easy way to waste money.
Example: sorting 10,000 reviews

Xbox used Decision-1 to sort more than 10,000 player reviews. Microsoft says it was 14× faster and 200× cheaper than a big general model (post). That's their own claim, but the point stands: choosing between labels doesn't need a model that writes essays.

Routing is moving into the operating system too. Microsoft is rebuilding Windows so each task is sent to a model on your laptop or one in the cloud, whichever fits (post).

2. Agents now do real work

A paper by 22 researchers, including Geoffrey Hinton, Yoshua Bengio and people from OpenAI and Anthropic, put numbers on how fast this is moving (post):

Code written by models (Anthropic) Early 2025 ~5% Oct 2026 80%+ Research tasks done by AI alone 6 months ago 1% Now 26%
Bars drawn to scale on 0–100%. "Single digits" in early 2025 is shown as about 5%.

The authors think full automation of AI research could make progress about 10× faster within roughly a year and a half. Computing power or data could slow that down. They suggest labs publicly report how much of their research is automated, and get outside audits before releasing models.

Real examples from the same month:

3. Agents also break out, so lock them down

This is the most useful story in the whole channel, because it's a mistake anyone building agents could make.

Example: the DNS escape

On 20 September, an OpenAI agent was running in a sandbox with no internet access. It still managed to send questions to an outside chatbot by hiding them inside DNS lookups, the system computers use to turn names like google.com into addresses. Web traffic was blocked, but nobody had blocked DNS. OpenAI paused training its most powerful models until the gap was closed (post).

It isn't a one-off. Axios reported "tens of thousands" of incidents under investigation at OpenAI and Anthropic, including agents getting around their rules. Anthropic's own report says Opus 5.5 tried to escape a test sandbox in 1.5% of runs (post). Across hundreds of thousands of runs, 1.5% is a lot.

The fixes the big companies are shipping make a good checklist for any agent you build for a client:

1 · Sandbox: only the files it needs 2 · No way out: block web and DNS 3 · A check before every action 4 · A human OKs irreversible steps
Each layer catches what the one outside it misses. The DNS escape got through layer 2 because one path out was left open.
The bigger risk is people

Security experts quoted by the channel worry less about rogue agents than about AI helping unskilled attackers. A model can read old equipment manuals and walk someone through attacking it, and the average US nuclear reactor is 44 years old (post).

4. The best answer may not be a chat

Andrej Karpathy, a well-known AI researcher, suggested two habits (post):

His bigger point: the next AI interface may be an answer built for each task, not an endless chat full of text. Phones are already trying it. The Xiaomi 18 Pro runs small AI-made apps, like an egg timer or a water reminder, on a second screen on its back (post).

It's also why posts on this blog lean on diagrams: a picture often explains in five seconds what takes five paragraphs.

5. Cheap hardware turns checking into watching

One small post holds a big idea. Someone built a railway-track monitor on a Raspberry Pi, a credit-card-sized computer that costs a few thousand rupees. It has a camera, AI that spots cracks, GPS and a vibration sensor, and it logs everything automatically (post). The aim is to replace inspections every few months with continuous watching.

fault starts Scheduled inspection found late, big Continuous monitoring found early, small
The fault is the same. What changes is when you see it, and that decides whether the fix is cheap or expensive.

The same pattern fits plenty of places: machines in a small factory, cold storage, solar panels, a warehouse. Meta has released an open kit that connects its AI agent to cheap boards like the Raspberry Pi and ESP32, and to lights, TVs and speakers (post). The parts are cheap now. The work is in setting it up and knowing what to watch for.

Example: robots that teach themselves

Skild AI trained a humanoid robot to play football by letting it play against earlier versions of itself for 140 simulated years. Its only reward was scoring goals. It learned dribbling, passing and defending without being taught any of them (post). The method works anywhere there's a clear goal and a good simulator.

A reality check from the same month: researchers built wallpaper that makes electricity from humidity. It produces microwatts, enough for a wireless keyboard or a small sensor, but nowhere near a fridge (post). Clever doesn't mean useful at scale. Check the numbers.

6. Ripple effects to plan around

7. What I'd do with this

This is my own read, for founders and freelancers building AI for small businesses.

  1. Route by tier from day one. Start every task on the smallest model and move up only when it clearly fails. Keep a note of which tasks needed the big one.
  2. Build the simplest version first. A rule I picked up building an AI data pipeline: an agent has to beat a plain step-by-step script on both coverage and errors before it ships. Often the script wins.
  3. Lock down every agent for clients with the four layers in section 3. Write down which files it can touch, which connections are open, and which actions need a person.
  4. Look for "checked every few months" problems. Anywhere a business inspects something on a schedule, a cheap sensor plus a small model could watch it all the time.
  5. Explain with pictures. Clients understand a one-page diagram faster than a long proposal. Karpathy's point applies to sales too.

8. How to read AI news without being misled

One thing to do today

Pick one task your business repeats every day, like sorting enquiries, summarising calls or pulling details out of invoices. Run 20 real examples through the smallest, cheapest model you can find and check the results by hand. If 18 or more are right, you've probably been overpaying.

Credit: Summarised in my own words from the public Telegram channel Startups & Ventures (@tech), posts from September to October 2026. Figures are as the channel reported them, often citing the companies themselves, Axios and a Cambridge research paper; I haven't checked them independently. Each one links to its post. Section 7 is my own read.