2.9.30
Released 8 Nov 2026
Verilog Atlas runs the reader's own verilog hdl simulator through Shell. Version 2.9.30 is available in 13 languages with no account needed.
.3 entriesError tb_counter.sv1 matchestb_counter.svloadedtb_counter.sv+1simulateexit 0Released 8 Nov 2026
Installer size
Single .exe file
Interface languages
WSL and SSH support
No telemetry data
Verilog simulation runs a design and testbench in simulated time, and Verilog Atlas drives your installed simulator through the Shell tool to read the text output. No account needed. A passing simulation shows only that the tested cases behaved as expected. It does not prove the design is correct or works on a real board.
Verilog Atlas version 2.9.30 uses grep to locate the error line in the source file and then invokes read_file to load the entire module for context. Fix it. edit_file proposes a diff to change the blocking assignment to non-blocking. You review the change in Ask first mode and accept the update. Shell runs the simulator command to verify the fix with a passing exit code. This approach simplifies rtl verification tasks effectively for every designer.
grep Error → 1 match
read_file tb_counter.sv → loaded
edit_file tb_counter.sv → +24 lines
Shell simulate → exit 0Verilog Atlas orchestrates rtl verification by using glob to locate design files and read_file to parse their port lists for the agent, so it writes code. Use Shell. The agent creates a testbench using write_file and includes a clock generator. You review the testbench and run it yourself; a pass shows only the tested cases. Verilog code for time borrowing latch helps clarify timing issues in your design. The tb_counter example has 10-16 lines and uses 58 character limits.
glob *.v → 1 match
read_file design.v → loaded
write_file tb.sv → saved
Shell compile → exit 0Use ocr to read text from a waveform screenshot so you can verify the design thoroughly today, and Shell opens the viewer to let you check the simulation results immediately. Fix errors now. Use grep to find FAIL in the log file right away. Read the design source with read_file to understand it fully. Run the testbench for system verification on your design code. Count the 1364 standard compliance for verification steps today carefully.
Shell grep log.txt → found FAILVerilog Atlas uses task to parallelize multiple testbenches while Shell runs each command to verify stability through real exit codes and grep finds errors. Write i2c rtl code. Cron schedules prompts on a schedule to automate repetitive verification steps. The task feature splits several testbenches across sub-agents for complex verification tasks. Shell runs terminal commands for builds to compile the design using your installed simulator tools. Grep finds FAIL, Error or x values in the simulator log, unlike a vhdl simulator.
task run_tests → started
Shell test1 → exit 0
Shell test2 → exit 0
Shell test3 → exit 0Verilog Atlas 2.9.30 runs your tools and shows results, so it handles systemverilog arbitrary vector sizes without extra work. It runs locally.
| Typical chat assistant | Verilog Atlas | |
|---|---|---|
| Runs tools | Suggests commands | Runs commands |
| Shows output | You paste output yourself | Shows output |
| Changes files | Shows diff | Proposes a diff you accept |
| Location | Cloud or local | The app runs locally on Windows 10/11. The model can be a cloud provider, local, or built-in. |
Students use Verilog Atlas for coursework to run verilog simulation on their designs and verify the logic with systemverilog testbench files for their projects. Check results. They review diffs to understand errors in their code logic.
Engineers rerun regressions, read logs, and accept fixes in Ask first mode, so daily verification remains essential for verification tasks and keeps the workflow effective. Run the tool. This ensures consistent results for all designs every single day.
Researchers use Verilog Atlas to verify their own designs by running Shell commands that compile and simulate the code while the agent reads the results. Verified. It supports 13 languages for global teams and users.
Yes, it is a process where a design and testbench run in simulated time to print messages, and Verilog Atlas drives the simulator through the Shell tool to check outputs. It depends. Cloud endpoints receive the prompt text, while local models keep everything on the PC.
Yes, verilogsystem.com is the official Verilog Atlas website, and you can verify the installer by comparing its SHA-256 checksum with the published manifest using the certutil command in Windows. It is static. Press the Send feedback button inside the app for support.
Verilog Atlas is not a simulator, but it runs your own installed simulator through the Shell tool and reads the text output to parse the results. You choose the mode. The agent does not replace the simulation software you already use.
A testbench is a module without ports that instantiates the design under test, generates a clock, applies reset and stimulus, and checks outputs with assert statements to verify correct behavior. It is self-checking. Verilog Atlas can write a complete testbench for you today.
Windows 10 and Windows 11 (x64) are the supported operating systems for Verilog Atlas, an autonomous AI agent that runs locally without requiring an account. It is free. The current version 2.9.30 is ready for download on these platforms.
Yes, chats, working folders, and API keys stay on the machine while prompts go only to the chosen model endpoint, so with a local model nothing leaves the PC. Secrets are redacted. No telemetry and you control the network features.
Verification is the process of running simulations to check design logic, and Verilog Atlas automates this by running your simulator, reading the log and proposing diffs you review. Review them. Yes, changes appear in Ask first mode before any edit.
Verilog Atlas runs your simulator and testbench, and Version 2.9.30 is ready for Windows 10/11. Download the 34 MB agent now. You stay in control.
Download Verilog Atlas for Windows ↗The website pages exist in 20 languages; the app interface has 13.
Product details ↗ Model configuration ↗ Workflow library ↗ Download page ↗ FAQ page ↗ Privacy policy ↗