agent-exchange: a toolkit for layering messaging and coordination on top of terminal-based agents, like Claude Code and Codex. Agents exchange messages across harnesses through a unified CLI.
Sessions can run locally, distributed, and in containers, addressed the same way everywhere.
Website: krasserm.github.io/agent-exc…
GitHub: github.com/krasserm/agent-ex…
I mostly stopped writing /goal prompts and coding-agent instructions myself. Instead: I ask an agent to analyze the codebase from perspectives I pick (design, correctness, perf, ...) and produce a report, and that report is the only thing I actually review and refine.
Building agent skills takes the same discipline as composable software: one skill, one responsibility. Composite skills use other skills instead of reimplementing them, and no skill grows into a mega-skill that does everything. The payoff is leaner context.
"code actions", "code mode", "programmatic tool calling", ...
Introducing Search as Code, our new search architecture for AI agents.
It writes Python that calls our search stack directly, instead of looping through function calls one at a time.
Available in the Perplexity Agent API, and now default in Computer.
research.perplexity.ai/artic…
An autonomous ML researcher built as a Claude Code dynamic workflow, generated from a spec:
- generate a technology-neutral workflow spec from Hugging Face's ml-intern
- generate a workflow script from the spec, on top of HF skills
- run the workflow script with any ML task
The workflow successfully ran for 1 hour on a sample fine-tuning task, incl. error recovery on failed HF jobs, on a first attempt. More on my spec-driven research automation experiments at gradion-ai.github.io/agents-…
Claude Code workflows are essentially programmatic tool calls taken to the next level. Instead of composing low-level tool calls into "code actions", generated scripts compose agent executions with a Claude Code specific workflow DSL.
Agents plus asciinema give you natural-language editing of terminal screencasts. A .cast is JSON Lines of [interval, code, data] events, so trimming, speeding, cutting, and (optionally) redaction all reduce to operations a model can emit as a small JSON plan.
The full cast never has to enter the model's context: an analyze step returns a few-hundred-token summary of gaps and relevant content, and the model reasons over that. Lossless to rendering. gradion-ai.github.io/agents-…
Martin Krasser retweeted
Introducing ml-intern, the agent that just automated the post-training team @huggingface
It's an open-source implementation of the real research loop that our ML researchers do every day. You give it a prompt, it researches papers, goes through citations, implements ideas in GPU sandboxes, iterates and builds deeply research-backed models for any use case. All built on the Hugging Face ecosystem.
It can pull off crazy things:
We made it train the best model for scientific reasoning. It went through citations from the official benchmark paper. Found OpenScience and NemoTron-CrossThink, added 7 difficulty-filtered dataset variants from ARC/SciQ/MMLU, and ran 12 SFT runs on Qwen3-1.7B. This pushed the score 10% → 32% on GPQA in under 10h. Claude Code's best: 22.99%.
In healthcare settings it inspected available datasets, concluded they were too low quality, and wrote a script to generate 1100 synthetic data points from scratch for emergencies, hedging, multilingual etc. Then upsampled 50x for training. Beat Codex on HealthBench by 60%.
For competitive mathematics, it wrote a full GRPO script, launched training with A100 GPUs on hf.co/spaces, watched rewards claim and then collapse, and ran ablations until it succeeded. All fully backed by papers, autonomously.
How it works?
ml-intern makes full use of the HF ecosystem:
- finds papers on arxiv and hf.co/papers, reads them fully, walks citation graphs, pulls datasets referenced in methodology sections and on hf.co/datasets
- browses the Hub, reads recent docs, inspects datasets and reformats them before training so it doesn't waste GPU hours on bad data
- launches training jobs on HF Jobs if no local GPUs are available, monitors runs, reads its own eval outputs, diagnoses failures, retrains
ml-intern deeply embodies how researchers work and think. It knows how data should look like and what good models feel like.
Releasing it today as a CLI and a web app you can use from your phone/desktop.
CLI: github.com/huggingface/ml-in…
Web + mobile: huggingface.co/spaces/smolag…
And the best part? We also provisioned 1k$ GPU resources and Anthropic credits for the quickest among you to use.
A pattern for making older repos more agent-ready. Use a coding agent to detect constraints, invariants, patterns, and symmetries at the
architecture/design level. Detect exceptions and explore consolidation options. Let the agent fix exceptions and consolidate the codebase.
Concrete example from a recent pass on github.com/gradion-ai/freeac…. The agent identified 8 constraint categories (type system conventions, config persistence patterns, async/sync boundaries, module dependency direction, widget factory signatures) and 7 consolidation opportunities. All implemented in a single session.
The detected constraints are written to concise, topic-scoped files that give agents initial guidance without overwhelming context. With these in place, agents produce code that matches existing patterns on the first pass instead of after course corrections. A more consistent codebase feeds back into more consistent agent output.
New blog post and Claude Code plugin: Code Actions as Tools
Programmatic tool calling becomes more powerful when code actions are saved as reusable tools, enabling agents to evolve their tool libraries at runtime.
🔧 Code actions invoke tools via executable code
💾 Working code actions are saved as reusable tools
🧩 Typed interfaces are separated from implementations
🚀 Agents can accumulate new capabilities at runtime
🧬 Tool libraries evolve based on agent experience
♻️ Reusable tools avoid redundant code action generation
Blog post: gradion-ai.github.io/agents-…
Claude Code plugin: gradion-ai.github.io/ipybox/…
Martin Krasser retweeted
Replying to @wergieluk
It uses Anthropic's srt to sandbox the IPython kernel that executes code, and optionally individual MCP servers.








