ToolBB-0046

instr-core: a safety layer between AI agents and SCPI instruments

instr-core checks each SCPI command an agent plans against the instrument's schema and dry-runs the plan before anything touches hardware. Checks cover ranges, compliance settings, output state and command order, and real VISA runs need explicit confirmation. The first workflows are IV sweeps on a Keithley 2600, one paired with a DMM6500. The README shows no measurements.

Open original source github.com · Yuliang Jiang

Claimed
Why this evidence label?

README describes dry-run and confirmation flow; no measurement output from real instruments shown.

How we check entries
Preview image for instr-core: a safety layer between AI agents and SCPI instruments
The source's own preview image, from github.com.

Briefing

Each instrument's limits live in YAML or JSON schemas instead of a PDF manual the model has to read. instr-core parses a request such as a 0 to 5 V sweep with 10 mA compliance into a structured plan, validates it, and fails closed when no trusted schema matches the connected instrument.

The same core is exposed through MCP, a FastAPI service and a Tauri desktop app. Agent plans start in dry-run mode, and execution needs both a confirmation flag and a valid dry-run result. The project is marked pre-release.

From the GitHub API

Repository facts

Repository facts for rainfallmax/instr-core, from the GitHub API
Repositoryrainfallmax/instr-core
Stars1
LicenseMIT Permissive
LanguagePython
Last push8 Sep 2026 51 d ago

Tags

Report a problem with this entry