Troubleshooting
On this page
KES-P...: parse error
Check the reported line/column against language reference. Kessetsu is line-oriented; commas belong between connection pins and to is required.
KES-C... or KES-E...: compile/ERC error
Verify names, pin identifiers, physical units, one unambiguous GND, and that every required component pin is connected. Raw SPICE directives and unversioned model packages are intentionally rejected.
For external subcircuits, KES-C014 means the typed metadata, path, or compatibility value is invalid; KES-C015 means the declared resource bytes were not supplied; KES-C016 means their SHA-256 differs from the declaration; and KES-C017 means the file is not valid UTF-8 or does not contain exactly one matching .SUBCKT entry with the declared terminal count. Native CLI commands resolve resources relative to a file-based .kess source; stdin cannot bind these files. On Web, select the exact local file in View → Circuit details…. Browser-incompatible models need the CLI. No generic model is substituted. See the model catalog.
Installed on Windows, but the agent cannot find kess
The installer updates User PATH and the PowerShell session executing it. An already-running IDE/agent or its parent process may still hold the previous PATH. Restart that application, or give your agent the full launcher path printed by the installer. This is not necessarily an installation failure. In ordinary PowerShell you can also run:
& "$env:LOCALAPPDATA\Kessetsu\bin\kess.cmd" --version
For a custom installation directory, use its printed command path instead.
Simulator not found or exit 3
Run the CLI with the release-provided simulator instructions, or set KESSETSU_NGSPICE to the full Ngspice executable path. Kessetsu probes the executable version before use; a directory or incompatible binary fails closed. Use --include raw-log --format json only when diagnosing simulator output.
Assertion returns ERROR
The required analysis or signal is missing or incompatible. AC metrics need an AC source; transient metrics need enough samples, and THD needs at least two fundamental periods. The message on the assertion explains the exact missing condition. See simulation and assertions.
Output already exists
Generated files are never silently overwritten. Pick a new path or add --force after confirming the target. The source file itself cannot be an output target even with --force.
KES-I007 means a SPICE or LTspice export depends on an external model file but the requested output directory differs from the source directory. Write the export beside the .kess source so its validated relative include remains usable. Kessetsu does not silently copy or redistribute the model.
KES-I008 means the external .kessreq file could not be read. Check the filename and permissions; Kessetsu does not fall back to inline assertions when an external requirement path was requested.
A shared URL will not open
Kessetsu accepts kessetsu.share.v1 envelopes whose embedded compile schema is compatible (kessetsu.compile.v4 through v9), limits compressed input and decompressed source size, and verifies the embedded package manifest. A truncated URL, unsupported compile schema, or modified package manifest is rejected instead of partially loading. Ask the sender for a URL created by a compatible release (and load any referenced external local model files separately).
Web simulation does not start
Check the Simulation panel's status first:
- Checking source: wait for the automatic check after your edit.
- Fix source errors: choose Show source errors to restore Source, then click the diagnostic's reported line. Simulation/export wait for a valid source.
- Model file needed: choose Choose model files, then select the exact declared library. A wrong file remains rejected; see its diagnostic for hash or interface mismatches.
- No analysis configured: add an analysis such as
simulate opto Source. A schematic and export do not require a simulation command. - Results out of date: source or model bindings changed; run again before using results.
Confirm that JavaScript, WebAssembly and module Workers are allowed and reload once. The production build pins and integrity-checks the runtime. Browser simulation runs locally; the Web Hub sends no telemetry and has no server-side fallback.
A completed run with no assertions is not a verified requirement set. Add measurable
assert statements, or use the first circuit tutorial for a five-check example.
Browser draft recovery is unavailable
Browser storage may be disabled, full or restricted. The circuit remains editable; choose Save a .kess copy in the warning to save/download a portable file. Save in browser cannot succeed while storage is blocked, and a failed save keeps the unsaved marker. Native file saving can still succeed independently. Restoring storage and saving again clears the recovery warning; clearing site data removes existing drafts, so keep a file copy first.
If a file save reports that it saved an earlier version, edits were made while that write was pending. The current source remains unsaved: press Save again. Do not interpret an old file-write completion as a checkpoint for newer changes.
KiCad/LTspice warning on open
Read the export capability/loss message. KiCad files embed portable Kessetsu symbols and may report a symbol-library-table warning; LTspice uses its standard symbol library. Connectivity is release-smoke-tested, but Kessetsu assertions remain in the .kess source and are not editable-EDA assertions.
A page or research-data tool could not open
A missing page module, interrupted download or application error shows a recovery message instead of leaving a blank screen. Check the connection and choose Reload page. If just the research-data tool failed, Return to editor dismisses the error without replacing your source: save/download your circuit before reloading if draft storage is unavailable. Reload does not clear stored browser drafts, but in-memory model files, CSV working sets and study results must be reselected or reimported. Download Results JSON before normal reloads when you want to preserve a study. If the error persists, report the page, browser version and any console diagnostic; do not clear site data as a first recovery step.
Report a problem or blocked workflow
Use Help → Report a problem in the editor, or the site's Feedback link.
Describe the engineering task, steps or CLI command, expected and actual result, exact
diagnostic, Kessetsu version and browser/OS. A small anonymized .kess example helps us
reproduce the problem. Reports are public: do not attach confidential circuits, credentials,
proprietary model libraries or files you cannot redistribute. GitHub requires an account
to submit a report; using Kessetsu itself does not.