Claude Code's Workflow Tool Offers Real Power but Suffers from Poor Adoption and Flawed Defaults

·2 views

Claude Code features a dynamic workflow system built on a JavaScript-like scripting dialect that lets users orchestrate multi-agent tasks through primitives such as agent, pipeline, parallel, and nested workflow calls. Unlike traditional agent-team setups, Claude Code's harness manages orchestration directly, reducing token consumption and avoiding dependence on a lead model to babysit subagents. Despite these structural advantages, the feature has seen minimal real-world adoption — a search of the top 20 GitHub results for 'ultracode' found zero repositories shipping actual Claude Code workflows, with most instead porting the concept to rival tools like Codex. A key flaw undermining practical use is that Claude is not properly instructed to select appropriate models per workflow phase, defaulting all worker agents to the same heavyweight model as the main session, which drives up costs unnecessarily. Critics and users alike view the current workflow setup as impractical and expensive, pointing to gaps in documentation and default configurations as the primary barriers to wider adoption.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Purdue Study: Removing Teacher Model Boosts Small AI Reasoning Performance

Researchers Yi Ding and Ruqi Zhang from Purdue University found that teacher supervision in on-policy distillation introduces noise rather than useful guidance, with larger teacher models producing even more signal degradation. Their analysis revealed that training gains in standard distillation come almost entirely from penalizing low-probability tokens, not from transferring teacher knowledge. Building on this insight, the team developed On-Policy Self-Adaptation (OPSA), which replaces the teacher with entropy-adaptive penalties calculated directly from the student model's own distribution. Tested on Qwen3-1.7B, OPSA improved AIME24 Avg@32 performance by 35.41 points, outperforming standard teacher-guided distillation by 16.77 points. The approach also eliminates the computational overhead of loading and running a separate teacher model during training.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds AI law firm template where buyers own their own API keys

A developer building CounselForm AI 2.0, a Framer template for law firms, designed the AI layer around a Bring Your Own Key (BYOK) model so buyers retain full control of their AI infrastructure. The template features a tool called Ask Lexora, which lets website visitors explore firm expertise through either structured guided questions or a natural-language AI mode. To keep API credentials secure, a Cloudflare-based server-side layer sits between the Framer frontend and the AI provider, preventing secret keys from being exposed in client-side code. The AI is grounded in a curated Knowledge Sync workflow using approved firm content, rather than allowing the model to generate unsourced or fabricated firm-specific answers. This architecture ensures each buyer bears their own inference costs and is not dependent on the template seller's infrastructure or subscription.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Build a Production-Ready ASP.NET Core Web API with JWT, CQRS, and Clean Architecture

A developer guide published on DEV Community walks through configuring a production-grade ASP.NET Core Web API using a range of modern tools and patterns. The setup covers database integration via Entity Framework Core with SQL Server, ASP.NET Identity, and JWT-based authentication and authorization. CQRS is implemented using MediatR to cleanly separate commands and queries from controller logic, while FluentValidation handles input validation. A global exception handler is used to standardize error responses across the API, replacing repetitive try-catch blocks in individual controllers. The article also addresses CORS configuration, Swagger setup, and Clean Architecture principles to keep the codebase maintainable and scalable.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Google shares five rules for building trustworthy AI agent evaluations

A Google Developer Relations team has published guidelines for designing reliable evaluations of AI agents, drawing from their work building Agent Skills for Google products on GitHub. The team warns that poorly designed evaluations waste token budgets and generate misleading performance signals, much like deploying an API without unit tests. They recommend understanding the constraints of your evaluation framework — such as Harbor or Inspect AI — before writing any tests, including how sandboxes, tools, and output capture work. To ensure evaluations are meaningful, the team advises writing prompts that require multi-step reasoning and reflect real-world complexity, so results genuinely reflect the agent tool's value rather than the base model's existing knowledge. The guidance is part of a broader series on scaling AI tools beyond informal 'vibe testing' toward structured, automated benchmarking pipelines.

0 comments Read more at DEV Community