The EDAUtils AI SDK puts a planning and execution layer over your existing flows and tools. You state a goal in plain words - "build the SoC from its IPs", "run CDC on the timer IP", "what must I rerun since the last green commit" - and the SDK turns it into an ordered plan of steps owned by domain specialists, shows the plan, and runs it when you confirm (plan mode) or straight away (act mode). The specialists drive real tools and report evidence - logs, reports, files - not prose.
The fleet
A Flow Manager routes each request to the right Lead, builds plans that span Leads and answers "which agent fits my task" through the Advisor. Seven domain Leads plan and execute for their domain and adapt a plan when a step fails; about 40 specialist agents each do one narrow job.
| Lead | Agents |
|---|---|
| SoC Integration | ingest, connectivity, delta, Tcl generation, validate, IP-XACT, top, elaborate, formal connectivity check, pinmux |
| Verification (DV) | build and compile, regression run, triage and debug, waveform debug, testplan, testbench and testcase generators, coverage analysis and closure, constrained-random stimulus, PyUVM testbench, formal property agents |
| RTL | lint analyzer, formal CDC, synthesis run and analyzer, equivalence checker |
| FE-CAD | RTL parser, lint, CDC, CDC advisor; runs the Expert System next to the Advisor |
| Sign-off | IP package; IPQC runs as a FECAD flow the Lead plans |
| DFT | MBIST generator, scan lint, ATPG, DFT integration |
| Infrastructure | create structure, setup environment |
What it does
- SoC integration and derivative SoCs - build a top from IPs with a reviewable, repeatable pipeline; architecture-driven integration; derive a variant SoC from a tagged base.
- RTL - parse and structure, lint, synthesis with Yosys by default, equivalence, CDC with formal, debug and fix proposals applied only through a gate that proves the fix.
- Verification - testplans, testbenches, testcases, formal properties, regression runs and triage, coverage closure.
- Static checks - lint, CDC and RDC, UPF and SDC lint, IP-XACT lint, with the CDC, RDC and Lint Expert Systems for waiver decisions.
- DFT and sign-off - scan lint, MBIST, ATPG, IPQC maturity gates, waivers with owner and expiry, and a collateral-consistency check that fails the gate on cross-file errors.
- FE-CAD flows and EDAUtils tools - the FECAD flow framework and the EDAUtils command-line tools, including Baya.
Where you use it
The same plan engine sits behind every surface: a WebGUI with plan cards and live step rows, a CLI, a terminal UI, an MCP facade and a Python API, and the VS Code and Cursor extensions. A single edautils binary runs in laptop mode with an embedded runtime or against a central server shared by a team, with local, LDAP or SSO login.
Safe by design
- One guarded LLM router for every model call. A content guard, on by default, redacts passwords, API keys, tokens and credentialed URLs from prompts and attachments.
- A provider policy to allow or deny hosted providers, an optional enterprise gateway, and your own provider keys or a local model server. The SDK runs inside your network.
- Deterministic engines for what must be exact - connectivity, address maps, register facts, equivalence. The LLM plans, explains and suggests; it does not silently wire, sign off or waive.
- Flat, whole-design runs are the default. A reduced path such as hierarchical or per-IP runs only when you ask for it or the full run has actually failed, and the report says which path ran and why.
Extend it
Add your own specialist with the new-agent scaffolder or a YAML manifest, bring an agent built in any framework through the external-agent contract, plug in MCP servers, and register your licensed vendor tools behind the same plan. Farm execution on IBM LSF reaches tool steps, test runs and flow recipes, with jobs sized from measured peaks.
Install
Requires needs Python 3.10+ on Linux; no JRE required. The release bundle also carries the two IDE extensions as .vsix files.
tar xzf edautils-ai-sdk-<version>.tar.gz
cd edautils-ai-sdk-release-*/
./install.sh # OS packages, virtualenv, licence timer
cd binary
export EDAUTILS_AI_SDK_ROOT=$PWD
export EDAUTILS_AI_LICENSE_FILE=$PWD/edautils_license.json
# point it at a model (local Ollama is cheapest):
export OLLAMA_BASE_URL=http://localhost:11434
export DEFAULT_LLM_PROVIDER=ollama_llama3_1_8b
# on-demand mode -- nothing to start, Leads and agents spawn per request:
edautils --laptop-mode ask --target fecad "parse gpio.v"
edautils --laptop-mode tui # full TUI
# or the full stack, then the flagship end-to-end example:
./scripts/start_fm.sh # Flow Manager on 8023 (WebGUI + API)
./scripts/start_dev.sh -fecad # one domain at a time on a single host
python3 examples/104_dft_lead_soc_top_end_to_end/run.py
./scripts/start_dev.sh --stop
# IDE extensions -- bundled, no marketplace account needed:
code --install-extension eu_vscode/edautils-ai-2.0.0.vsix
cursor --install-extension eu_cursor/edautils-ai-cursor-2.0.0.vsix
# full steps for every mode: GETTING_STARTED.md in the tarball root
The release installer offers to install the latest designplayer-shell and FECAD and the free EDA tools (Yosys, SymbiYosys, Verilator, Icarus Verilog and others) into one directory, in user space. A signed license file gates the SDK; evaluation licenses are time-limited. For evaluation or purchase write to sales@edautils.com.