Dev Solves Cross-Provider AI Tool-Calling Gap in Healthcare App Using Unified SDK

·1 views

A developer building a clinical decision-support tool was asked by compliance to add a second AI model from a different provider to independently verify medication-allergy conflict checks. The challenge arose because OpenAI and Anthropic handle tool-calling in structurally different ways, requiring separate integration logic for each provider. Rather than rewriting the tool-calling loop twice, the developer used an open-source library called shapecraft, which abstracts provider differences behind a single unified function. This allowed both GPT-4o and Claude Haiku to run the same medication and allergy lookups with identical code, changing only the model constructor between calls. The approach eliminated manual handling of provider-specific message formats and significantly reduced the rewrite effort the developer had anticipated.

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)

Agentic-Framework v4.1.0 and v4.1.1 Fix Security No-Op Bug and Migration Flaws

Developer and maintainer of agentic-framework, a Claude Code plugin that orchestrates 21 specialist subagents, shipped two releases this week: v4.1.0 and v4.1.1. Version 4.1.0 focused on standardizing agent configurations that had drifted from enforced settings, upgrading eight agents from Sonnet to Opus, and adding a new validator check to prevent future configuration drift. The migrate-legacy script was also hardened after two bugs were found that could silently mask incomplete cleanup and block users with edited CLAUDE.md files. Version 4.1.1 delivered three smaller fixes, including a runtime-generated stats table, a stricter frontmatter parser that now fails loudly on malformed input, and a corrected secret scanner that no longer falsely flags shell variable expansions as hardcoded secrets.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Python Magic Methods Explained: How Dunder Methods Power Custom Classes

Python's special methods, commonly called magic or dunder methods due to their double-underscore naming, allow custom classes to integrate seamlessly with built-in Python syntax and operators. By implementing methods such as __str__, __len__, __eq__, and __iter__, developers can make their objects behave like native Python types including lists, dictionaries, and integers. Key categories covered include representation, sizing and ordering, iteration, callable behavior, and context management via __enter__ and __exit__. A practical demonstration combines nine dunder methods into a SmartBatch pipeline that functions as an iterable, comparable, and callable context manager. The guide is part of an ongoing Python learning series aimed at helping developers unlock more expressive and Pythonic class design.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AGENTS.md Works Best Written as Code, Not Prose, for AI Coding Agents

Developers using AI coding agents often face a recurring problem: the agent repeats the same mistakes each session because it retains no memory between conversations. A project-level file called AGENTS.md is designed to solve this by giving the agent a permanent set of instructions it re-reads at the start of every session. However, most users see little improvement because they write the file as descriptive prose, which AI agents tend to treat as ambiguous background rather than actionable directives. The key distinction, according to the author, is that AGENTS.md should be written like code — with precise, imperative rules covering commands, forbidden patterns, and restricted files — rather than like human-facing documentation. Anthropic data cited in the article suggests engineers fully delegate only 0–20% of AI tasks, and proper agent configuration, not model capability, is identified as the missing factor.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AI Boosts SRE Productivity by Automating Routine Tasks, Not Replacing Engineers

Artificial intelligence is reshaping Site Reliability Engineering workflows by handling time-consuming mechanical tasks such as alert triage, log summarization, runbook drafting, and post-mortem write-ups. According to Dr. Samson Tanimawo of NovaAIOps, AI effectively covers around 30% of work at both the start and end of incident management, while humans remain essential for the critical middle phase involving judgment, decisions, and stakeholder communication. AI falls short in areas requiring experience-based instincts, handling novel failure modes, navigating organizational dynamics, and bearing accountability for outcomes. Tanimawo argues that SREs who integrate AI tools into their on-call workflows can manage two to three times more incidents without sacrificing quality. He recommends starting simply by feeding alerts into tools like ChatGPT or Claude to explore possible causes before incorporating AI more deeply into operational tooling.

0 comments Read more at DEV Community