EDA Bridge Runtime

Ask naturally. Reach the right EDA. Keep the work recoverable and verifiable.

简体中文 ·

EDA Bridge Runtime is the shared, vendor-neutral execution path behind EDA Agent Bridges. Whether the Agent and EDA run on the same computer or connect over SSH, the user gets the same target selection, durable jobs, timing record, and evidence model.

It is not another EDA automation API and it does not replace the vendor Bridge. ADS and AnsysEM Bridges keep their native engineering knowledge; Runtime makes their execution predictable across Agents, hosts, reconnects, and long jobs.

What this changes for an engineer

What the public tests show

The chart reports median wall time from six bounded public test cases, with three trials per Agent and task. Both Agents used the same Runtime and Bridge path. Agent-heavy tasks show the largest difference; AEDT-lifecycle-heavy work is dominated by the EDA itself. This is an engineering baseline, not a universal Agent ranking. See the full method, pass rates, and interpretation boundary.

The checked ladder covers documentation evidence, exact idempotent replay, typed ADS and AnsysEM work, a real generated-input Momentum solve, and a one-turn cross-EDA workflow. Sanitized acceptance evidence is maintained in Acceptance.

The newest functional cases go from an empty project all the way to native results: ADS builds and simulates a six-instance circuit and freshly reopens a DDS plot; AnsysEM builds a three-layer two-port HFSS 3D Layout design, solves five points, and freshly reopens its native S-parameter report. Codex and Pi both completed each workflow with one Runtime call. These are one-trial functional acceptances, not statistical speed claims.

Start with one Agent profile

Install Runtime on the computer where the Agent runs:

python -m pip install "eda-bridge-runtime==0.1.0a28"
eda-runtime doctor

Create the isolated profile for the Agent you use:

eda-runtime agent-profile codex install
eda-runtime agent-profile pi install --help

The administrator selects vendor Skills and connection details once. Engineers then start the generated profile and speak naturally; they do not maintain SSH commands, metadata files, or Runtime logs by hand.

Install the matching vendor Bridge on each EDA host:

• ADS Agent Bridge
• AnsysEM Agent Bridge

If the Agent and EDA share one machine, register a local connection. If they are separate, register SSH. Both still pass through Runtime so audit, retry, target, and evidence behavior do not split into two systems.

Safety promises

• Every Agent-originated action carries a concise purpose.
• Mutations require a stable identity and are never blindly replayed.
• A disconnect does not imply that a long EDA job failed.
• Context tokens contain locators and fingerprints, never credentials.
• The append-only ledger stores fingerprints and bounded metadata, not chat transcripts or raw operation payloads.
• Vendor-specific behavior stays in vendor Bridges, not in the Runtime core.
• Runtime does not claim a solve, artifact, or persisted change without corresponding Bridge evidence.

Learn more

• How the pieces fit together
• Agent host, EDA host, and combined deployment
• MCP and Codex integration
• Pi Agent pilot
• Protocol schema
• Current scope

eda-bridge-runtime is public alpha software. Begin with disposable work and review the vendor Bridge's capability and evidence boundary before using it on important projects.