zhoushoujianwork/easyeda-agent

If you already do board design in EasyEDA Pro and want an agent to do the repetitive parts — checking pins, tidying silkscreen, standardizing parts, or starting a layout from a requirements paragraph — this project is aimed at you. It is not a general EDA alternative; it is an automation layer bolted onto one specific editor, and that narrowness is both its appeal and its main constraint.

The problem

A board project usually starts with a data sheet and a lot of cross-checking: confirm the exact ordering suffix, map symbol pins to footprint pads, then place parts and wire them without losing track of a net. Today most of that happens by hand in the editor, and screenshots are a poor way to verify connectivity. With this project the agent reads the real project data over the official eda.* API, performs typed schematic and PCB actions, and re-reads the result to compare pins, nets, geometry and save state. The change is that verification moves from eyeballing to reading back written data.

What's different

The mechanism is a three-part stack: an easyeda CLI and daemon, an in-editor connector extension, and an easyeda-agent skill installed into the AI client. That split matters because the same actions are exposed as CLI commands, as an Agent Skill and as a stdio MCP server, so an agent that supports skills can work from natural language, while scripts can call the CLI directly. The README documents offline validation — for example lib device validate --spec checks data-sheet evidence, geometry and pin-to-pad mapping before anything is written to the library. That pre-write check is the most interesting part: library creation is where silent errors propagate into every board later.

The trade-off is that the quality of the result depends on how well the agent follows the spec and how good the underlying data sheet is. The README itself tells the agent to stop and ask when a manual has ambiguous packages or missing dimensions, which is sensible but means the workflow is human-in-the-loop rather than set-and-forget. It also inherits the connector's dependence on the official API, so capabilities mirror what EasyEDA Pro exposes rather than something broader.

Who should try it

Good fit: an EasyEDA Pro user with a real project and a supported AI client who wants help with library authoring from a PDF, schematic cleanup, device standardization by LCSC C-number, silkscreen adjustment, or laying out a modest board from a written requirement. The published walkthroughs — an ESP32-S3 four-layer board from a requirements document and a private library plus edge silkscreen case — show the intended scope concretely. Poor fit: someone using KiCad or Altium, someone who wants a standalone schematic tool, or someone unwilling to review agent output before manufacturing. Also a poor fit if you only need to hand-draw a tiny circuit once.

Requirements and limitations

You need EasyEDA Pro plus the EDA Agent Connector, installed either from the plugin marketplace or by importing the .eext release file into the extension manager. The CLI and skill install via shell or PowerShell scripts that verify checksums and versions before replacing files; manual steps exist in the quick-start guide. On Windows the installer does not silently edit PATH, so a piped install means you add the directory yourself.

Expect ongoing upkeep rather than a one-off install: the connector, the CLI and the skill are separate pieces and all need to stay compatible, and the GitHub version must be checked against the README for the matching release. The project's license is MIT for the main code, but files ported from Easy_EDA_PCB_Beautify remain Apache-2.0, which matters if you redistribute. Finally, the automation is bounded by the official API and by what the agent can verify; keep a human review and the official DRC in the loop.

HotRepo's take

HotRepo's only stored observation is a weekly Go board placement of #19 with +122 stars for the week ending 2026-10-26, against a project created 2026-06-25. There is no comparable daily history, so persistence of interest cannot yet be judged; treat the number as a single dated snapshot. Before adopting, verify the connector and CLI release you install share the same skill version, since the three components move together.