u/Significant_Box_4066

We've been developing a skill to improve your agent skills by scanning past agent conversations and looking for inefficiencies to improve. It's called /skill-doctor:

• Crawls your past CC, Codex, or Warp convos
• Scores them for efficiency and code quality and aggregates failure points
• Proposes diffs to your skills that you'd actually merge

Breaking this down: your agent splits up agent convos into subagent batches, each given two scoring rubrics on a 0-1 scale from "poor" to "perfect."

• Efficiency: did the agent require extra human intervention or course correct around bad docs?
• Code quality: does the code follow the codebase's architecture standards?

Once scores are calculated, your agent filters to "failed" cases to look for patterns that a skill patch might solve. Agents love verbosity, so /skill-doctor calls out common pitfalls: Be reluctant to propose edits, and never monkey-patch addendums; edits should be holistic.

In the end, you get a nice report with skill improvements to review. Try it out:

> npx skills add warpdotdev/common-skills --skill skill-doctor

warp.dev/skill-doctor

Warp Factories are open, flexible infrastructure for building your own cloud software factory. This means deploying agents as automations at each step of software development: triage, spec, implement, review, verification with computer use, and automatic self-improvement of factory skills.

We've bundled a number of features based on our own setup building and managing Warp:

• Build your factory as code: Define agents, automations, and workflows in version-controlled code, with everything accessible through the API, SDK, and CLI.
• Connections for everything: Trigger agents from Slack, Linear, Jira, GitHub, and the Warp Factory MCP.
• Customize every agent: Choose the model or harness, personalize its instructions, and give it the skills, MCPs, permissions, and context it needs.
• Measure and improve over time: Track cost, quality, and throughput with built-in metrics, evals, and benchmarks, then use that data to continuously improve your factory.

We're onboarding a limited number of companies onto Warp Factories right now. For select folks, we are offering $10k of factory usage to help get you started. warp.dev/factories/request-access

Big news: Warp now has custom routers, letting you route tasks to models you choose by complexity or natural-language rules!

• Route to your preferred models by complexity (easy through hard)
• Or, route based on plain english rules. Ex. use one model for planning and another for well-scoped bugs

You can select any model you want to route to, with support for BYOK and BYO inference URLs.

Go to Settings > Warp Agent > Custom Routers

...As for the rest of the changelog, it was a big week from external contributors too. /changelog has the full list:

• gfurlan and senseFy expanded our CLI-agent ecosystem: Google Antigravity CLI (agy) support and rich status for the Droid CLI agent: https://github.com/warpdotdev/warp/pull/12380
• david-engelmann tightened MCP security by respecting the secret-redaction toggle when saving server config: https://github.com/warpdotdev/warp/pull/10839
• External contributors sharpened terminal fundamentals, with contributions from GeekLuffy, roor0, ShankyJS, and maxmilian.