kessetsu
Skip to content

Web Editor Guide

On this page

Open the Web Hub. No account or installation is required. Compilation and simulation run locally in your browser; circuit source and model files are not uploaded. See the tutorial for a complete first circuit.

Start or open a circuit

Use File → Examples for an RC filter, gain stage, power amplifier, reusable blocks or local-model examples. File → New circuit starts a document; Open .kess… reads a local source file. Rename the document through File → Rename… or the Share dialog. Example selection replaces the active source; save work before switching.

Menus support keyboard navigation: focus a menu button and press Enter or ↓; use ↑/↓, Home/End within it, → to open Examples, and ← or Escape to return. Escape closes a menu and returns focus to its button. Closing an Analyze dialog returns focus to Analyze. Ctrl+Enter runs the editor simulation only outside dialogs; Ctrl+S does not save the background circuit while you are working in a dialog.

File → Import SPICE netlist… accepts .cir, .sp, .spice and .net files in the declared import subset. A successful conversion opens ordinary editable .kess as an unsaved document. Unsupported content reports original line numbers and leaves the current circuit in place. You can also drop a .kess or supported SPICE file onto the workspace; the same validation and unsaved-work confirmation apply.

The Source panel is a text editor with language completion and diagnostics. Changes automatically compile, run ERC and update the schematic after a short delay. The header status reports checking, success or errors. Fix source diagnostics before exporting or running. An automatic check is structural verification, not a completed simulation. When an error blocks work, Show source errors restores Source even if it was minimized; click a diagnostic with a line number to jump to that location. While your edits are being checked, the panels say Checking source, not that they are ready to run.

Arrange the panels

Drag the dividers to resize Source, Schematic and Simulation. Each panel header has minimize and maximize controls; minimized panels can be restored. Use View → Reset panel layout to return to the default arrangement.

In Schematic, scroll to zoom around the pointer, drag to pan, and use Fit to see the whole circuit. Toggle the dotted grid in its header. Select a component—or click any wire segment—to highlight its symbol or net, reference, and value. In the .schematic-navigator inspector, a selected component shows its value/model provenance, maps each logical pin to the canonical net (selecting a pin follows and highlights that complete net), and displays a live Simulated readout (ΔV, I, and P, including RMS/average summaries when transient results exist). Editable components provide inline -10% / +10% quick-tweak and Apply controls that update the source and automatically rerun simulation, plus 1-click Plot V, Plot I, and Plot P buttons (and + Compare on nets and signals to overlay waveforms on the active plot). Use Find to search components or named nets and center them in the view. Reusable module instances appear as navigable groups while electrical compilation and simulation remain canonically flattened. The drawing's connectivity check concerns the schematic, not hardware.

Run and inspect simulation

Write the analyses you need (simulate op, tran, ac or dc) in source. Circuits with an analysis automatically load and run simulation on initial workspace load, when switching examples, after SPICE import, and when opening a shared URL (unless required external local model files are still needed). You can also press Run simulation in the Simulation panel at any time; progress and cancellation are shown there. Errors are not replaced with invented results.

Select an analysis tab and signal to inspect operating-point values or waveform/Bode/DC plots, including derived I(...), P(...), and differential V(A, B) traces alongside recorded node voltages and branch currents. Selected dataset tabs and trace overlays are preserved across quick-tweak reruns when those signals still exist. Hover over a plot for numeric values. Assertions show PASS, FAIL, ERROR or SKIPPED with their measured value and limit. Simulation without assertions is valid but does not prove requirements. The cursor snaps to the nearest recorded sample in the displayed physical axis, including nonuniform simulator timesteps and logarithmic frequency spacing; it does not invent an interpolated sample. Scroll to zoom around the pointer and use Reset zoom to restore the view. DC sweeps identify the swept source and use V or A from the analysis. Descending sweeps still plot smaller axis values on the left. The default trace favors OUT/output, then an asserted named voltage or another external voltage before internal-model vectors; all signals remain selectable.

AC magnitude is absolute signal magnitude: dBV is relative to 1 V, and current magnitude is labeled dB re 1 A. This is not output/input gain. Phase is the selected signal's angle, not a transfer-function phase. Use the gain/gain_at and phase measurements for supported output/input comparisons. Requirement measurements stay in their table: aggregate RMS, average, peak and analysis-specific checks are not drawn as instantaneous waveform limits. When the source records physical-part ratings, a separate Provided part limits table shows model stress, utilization, recorded conditions and citation. Its Within/Exceeds/Unavailable state is advisory and never presented as a requirement PASS or hardware-safety approval. Editing the source makes previous results stale: rerun before drawing conclusions. Old results are cleared rather than shown as evidence for the edited circuit; Run again uses the current source. A canceled run leaves the source unchanged. If a run fails, the panel shows the actual error and a troubleshooting link instead of accepted results.

A valid circuit with no analysis can still be exported. The Simulation panel explains how to add simulate op for DC node voltages and currents, and links to the other analysis types; it does not offer a Run action that can only fail. A successful run with no assertions explicitly says that no requirement checks were defined. See simulation and assertions and measurements for exact meanings and analysis requirements.

Go beyond one simulation

Kessetsu provides guided multi-step workflows in unified WorkflowDialog wizards to explore variations and validate data:

  • Parameter study (Analyze → Parameter study…): A 5-step guided flow (Method → Variables → Checks → Review & Run → Results) for bounded sweeps, tolerances, loads, temperatures, candidate objectives, and reports. It tracks explicit snapshots when the editor circuit changes and supports explicit opt-in run comparison against previous results. Follow the parameter studies guide.
  • Compare data (Analyze → Compare data…): A 4-step guided flow (Observed → Reference → Match → Results) to map local CSV measurements or references and compare them against another dataset or a completed simulation. Advanced CSV dialect, calibration (gain/offset), missing-value behavior, and provenance settings are grouped in collapsible sections. Follow the research-data guide.

These workflows are optional. A first circuit only needs Source, Schematic and Simulation.

Review a proposal from an external agent

Open Analyze → Work with an AI agent… for a provider-neutral handoff structured as a 3-step guided flow (Task → Proposal → Review):

  1. Task: Describe the outcome you own, then use Copy agent task or Download task file, which automatically advances to Proposal. Paste the task into ChatGPT, Gemini, Claude, Codex or another agent of your choice. You decide which external agent receives it; Kessetsu does not upload the circuit, contact a model provider or store an API key. The task binds the circuit name, exact source and source SHA-256 to the requirements, including a compact Kessetsu syntax guide, a complete working example, and authoritative reference links.
  2. Proposal: Load the returned kessetsu.agent-proposal.v1 JSON using Paste from clipboard & check or Upload reply file…, which verifies the format, checks source compatibility, and advances to Review.
  3. Review: The proposed source is shown as a line diff and compiled through the same local Core while the editor document remains unchanged. Run simulation verification with Run simulation to obtain real local simulation and assertion results. Apply to editor remains an explicit action in Review and becomes enabled only after that run completes; closing the dialog or stopping the run changes nothing. If assertions fail, error, are skipped or do not exist, the completed simulation is not presented as verified; applying it requires a second explicit confirmation.

If a reply is rejected or its assertions are not satisfied, use Copy correction task or Download correction file in Step 3. Send it back to the same agent, then paste the new complete reply into Step 2 (Proposal). The correction retains your original requirements and source hash, the rejected reply and actual local diagnostic/assertion evidence. It does not change the editor, automatically fix code, relax limits or send anything to an AI service. A blocked clipboard has a selectable manual-copy fallback. Source, request or model changes invalidate old feedback.

For example, a 3 V ±50 mV target is two root-level assertions after simulate op:

assert value(V(OUT)) >= 2.95V
assert value(V(OUT)) <= 3.05V

These are an excerpt, not a complete circuit. analyze blocks, voltage(OUT) and inline +/- bands are not supported Kessetsu syntax; the language reference describes valid forms.

Editing the reply, changing the requested outcome, changing the open circuit or selecting/clearing local model files invalidates prior review and simulation evidence. After a model-file change, the reply text is kept so you can check and test it again. Closing the dialog abandons pending file reads, review and simulation; late results cannot restore them. A completed review is kept across close/reopen when its inputs are unchanged. After acceptance, Analyze → Undo AI agent change restores the exact prior source as long as it has not since been edited.

The proposal summary is untrusted text. Compilation verifies supported syntax and schematic connectivity; simulation verifies only the modeled analyses and assertions in the proposed source. The dialog keeps the human request visible and highlights high-impact assertion, analysis, source, component and connection edits, but it cannot infer that agent-authored assertions cover every sentence. Neither step proves hardware, hidden requirements or an agent's broader claims. Local model files remain local and must already be bound for a proposal that depends on them.

Save and recover

Saving depends on browser capabilities, not merely its brand:

  • Browsers with the native file picker (typically Chromium): Save / Ctrl+S selects a destination on first use, then writes the same permitted file. Save As / Ctrl+Shift+S selects a different destination. Canceling the picker does not mark changes saved.
  • Browsers without that picker (including Firefox): Save in browser / Ctrl+S stores the document locally and clears the unsaved indicator. Download .kess / Ctrl+Shift+S makes a portable file copy; repeated downloads may receive numbered filenames.

Save indicates progress and does not start another write while one is pending. If you edit the circuit during a file write, the earlier version may finish saving but the latest edits remain unsaved; press Save again. Switching circuits never attaches the previous circuit's pending file destination to the new one. Canceling or failing an open/import operation retains the existing circuit and its selected save destination.

An unsaved browser draft is recovered when storage is available. The editor also tries to flush the latest source before a normal reload or page exit. If storage cannot preserve unsaved changes, it requests the browser's leave-page warning instead. Browsers do not guarantee this event on crashes or mobile app termination; keep a file copy.

Browser-local work is not cloud backup: clearing site data, private browsing or another browser/device can make it unavailable. Keep a downloaded .kess copy for important work. Circuit tools preserve a previous circuit for File → Restore previous circuit where available. If automatic draft recovery cannot write to browser storage, the editor shows a warning with Save a .kess copy. Explicit browser Save failures do not clear the unsaved indicator. The warning is separate from native file saving: a successful file save is still valid even when browser recovery is unavailable.

Select a local device model

Built-in examples using bundled .lib models (External Comparator, Threshold Memristor) automatically bind their bundled reference model in memory when selected from File → Examples, allowing immediate compilation and simulation.

For custom or modified external_subcircuit declarations, or to replace a model, open View → Circuit details… and select the file beside the declared resource, or use the inline Choose model files… action in Simulation or Schematic when models are missing or mismatched. Its exact hash and interface must match before compilation succeeds. Selecting a file alone is not validation; wait for Source valid. Files remain in memory only: reselect after reload, opening another document or sharing. Browser-incompatible models require the native CLI; there is no generic replacement. The model catalog provides example downloads and limits.

Export or share

Use Export in the main header and choose a format. Review format warnings, especially model dependencies and EDA limitations. Save source separately; a PNG is not an editable circuit. See export formats.

Exports are grouped by purpose: images/documents, editable schematics, simulation netlist, parts/handoff and structured schematic data. All advertised formats remain directly selectable. The download notice shows the chosen filename and format-specific warnings, including dependencies that must be supplied separately. To reopen work in Kessetsu, save a .kess from File instead.

Share opens a dialog where you can name the circuit, then copy its URL. This creates a snapshot, not a live collaborative document: recipients edit their own copy, and later edits do not update links already sent. Anyone with the link can read its circuit. If clipboard access fails, select and copy the displayed link manually. Changing the name requires a new link. Closing abandons pending creation; late completion cannot rename the circuit or change its URL. Reopening starts a fresh sharing session for the current source. The link carries source and exact package identities, not current simulation datasets, file permissions or local model bytes. A recipient recompiles and runs locally. External models must be supplied separately under their license terms. Large sources produce longer links; no server-stored short-link service is currently provided.

For compilation, simulation or storage failures, consult troubleshooting. Help → First circuit tutorial and Help → Troubleshooting lead directly to these starting and recovery paths. Export, Circuit details and Analyze dialogs also link to their relevant guides without requiring you to search the full documentation.