AI Functions: Runtime Code Generation with Automated Verification

AI Functions is a new project from Strands Labs built on the Strands Agents SDK that enables runtime AI code generation with continuous automated verification. Instead of just generating text for humans to integrate, it produces code that runs inside your application at call time, returning native Python objects like DataFrames, Pydantic models, or database connections.
How AI Functions Work
The core abstraction is the @ai_function decorator. You write a Python function with a natural language specification in the docstring instead of implementation code. When the function is called, the decorator intercepts the call, constructs a prompt from the docstring (substituting arguments), sends it to an LLM, executes the generated code in your Python process, and returns the result as a native object.
Here's the basic example from the source:
from ai_functions import ai_function
@ai_function
def translate_text(text: str, lang: str) -> str:
"""
Translate the text below to the following language: {lang}.
{text}
"""
result = translate_text("The quarterly results exceeded expectations.", lang="French")
Key Differentiator: Automated Verification
The critical feature is post-conditions – plain Python assertions that define what correct output looks like. These execute on every function call, not just before deployment. If verification fails, the system automatically retries with the error as feedback. The human never inspects the generated code; the post-conditions handle verification every time.
Software 3.1 Concept
The article positions this as "Software 3.1" – an evolution from Andrej Karpathy's framework where Software 3.0 is "human prompts, LLM generates, human verifies." AI Functions represent "human specifies, LLM generates and executes, machine verifies – at runtime." The execution model differs fundamentally: the LLM isn't producing text for human integration but code that runs directly in your application.
This changes three aspects simultaneously: where AI fits in your software (runtime instead of just development time), what it produces (live objects you can call methods on instead of serialized text), and how you trust it (continuous automated verification instead of one-time human review).
📖 Read the full source: HN AI Agents
👀 See Also

ClaudeOrb: Chrome Extension Monitors Claude API Usage in Real-Time
A developer built ClaudeOrb, a free Chrome extension that displays Claude session percentage, weekly limits, countdown timers, Claude Code costs, and 7-day spending trends. The tool was created using Claude Code after hitting rate limits without warning.

Qwen3.6-27B SVG Generation with Closed-Loop Harness
A closed-loop harness using Agno and Pi agents iteratively improves SVG outputs from Qwen3.6-27B by rendering, feeding back PNGs to Qwen Vision, and judging results in two rounds.

Fixing OpenClaw's Blind Spots: Building a Sitemap to Fetch All Anthropic Blogs
OpenClaw's browser tool fails to discover all Anthropic blogs because they're hosted across multiple URLs. A user fixed this by feeding a generated sitemap, then packaged the solution as a shareable skill.
Anthropic's Model Hardware Standard: AI Agents Get a Unified Driver for Lab & Factory Devices
Anthropic's Model Hardware Standard (MHS) preview gives AI agents a standardized driver to operate lab and manufacturing instruments, reducing integration time from weeks to minutes.