Files & Logs
Where the editor stores its settings, templates, run logs, WebView data, and diagnostic log on your machine.
The editor keeps its settings, templates, run logs, and WebView data under one folder in your local app data, so they are easy to find, back up, or reset. Only the add-in's diagnostic log lives elsewhere.
%LOCALAPPDATA%\ExtrabbitCode.iLogicCode\Which typically resolves to:
C:\Users\<you>\AppData\Local\ExtrabbitCode.iLogicCode\What is stored
| Path | Purpose |
|---|---|
settings.json | Everything the editor remembers: all settings, keyboard shortcut overrides, your custom snippets and favorites, the inactive (private) external rule folders, debug watches, the templates folder and template order, the layout (split editors, sidebar width, log pane, expanded folders), and the usage-data consent and anonymous ID. |
logs\ | Default folder for the persistent run log, when enabled. |
logs\ilogic-runs-yyyy-MM-dd.jsonl | The persistent run log (JSON Lines), one file per day and one finished run per line. The folder and file name are configurable in Settings → Logging. |
templates\ | Default templates folder, used when you have not configured one of your own. |
recovered\ | Rule edits that couldn't be saved back into their document after you switched documents, or saved at all when iLogic Code was unloaded, one file per rule, named after the document, the rule and the time. Open a file to copy the text back. |
agent-instructions.md | Your own instructions for every agent session, created from a template the first time you open them. Plain Markdown; delete it to start over. |
agent\<document>-<id>\ | One folder per document for AI Agent sessions: rules\ (the document's rules as .vb files the agent edits), AGENTS.md (instructions, rewritten at every session start), and .ilogiccode\ (what was last synced, and the connection to iLogic Code's tools for the current Inventor session). agent\_scratch\ is used without a document. Safe to delete while no session runs. See AI Agent Privacy for what Claude Code keeps itself. |
WebView2\ | The WebView2 user-data folder: the editor's web cache. Safe to delete; UI state such as expanded folders is kept in settings.json. |
settings.json is plain, human-readable JSON and is created automatically on first run. You can copy it to another machine, or delete it to reset the editor to defaults. The editor also offers structured import / export if you only want to move part of your configuration.
settings.json is the only copy of your custom snippets, snippet favorites and inactive rule folders. Deleting it deletes them too. Export them first with Settings → Import / Export (the Snippets and iLogic Configuration sections) and import them again afterwards.
If settings.json is damaged (for example a hand edit left it without valid JSON), the editor keeps it as settings.corrupt-<date>-<time>.json next to it and starts with default settings. If it can't be read at all (for example while another program holds it), the editor starts with defaults and doesn't save settings until Inventor restarts, so the file isn't overwritten.
Run logs
The run log is in-memory by default and cleared when the editor restarts. With Persist log to file enabled in Settings → Logging, each finished run is appended to a file as it completes:
<log folder>\<log file name>-yyyy-MM-dd.jsonlA new file is started each day, so no single file grows without limit. Leave the folder blank to use the default logs\ folder shown above, and the file name blank to use ilogic-runs. These files can be reopened later in the Log Reader.
You can also export the current session's runs from the run log to a JSON file of your choice without enabling persistence.
Diagnostic log
The add-in writes its own diagnostic log, which records warnings and errors from inside Inventor, to your temp folder:
%TEMP%\ExtrabbitCode.iLogicCode\ExtrabbitCode.iLogicCode.logThe file rolls over at 5 MB and keeps the five previous files next to it (.log.1 to .log.5), so it never takes more than about 30 MB. If you report a problem, this is the file to attach. It is separate from the run log above, which records what your rules log.
For a detailed log of what the add-in does (activation, document events, rule runs), open log4net.config in C:\ProgramData\ExtrabbitCode\ExtrabbitCode.iLogicCode as an administrator and change <level value="INFO" /> to <level value="DEBUG" />. The change applies right away, without restarting Inventor. Set it back afterwards, as the detailed log grows quickly.