For developers
How the code is built, how to change it and how a release is made.
- Architecture: The three processes and how a change travels.
- Code map: Each folder of src/ and what lives there.
- The command engine and history: Commands, versions, runs, conflicts and undo.
- How the assistant works: A turn, its tools, drafts, pauses and the conversation log.
- IPC between window and main: Channels, the guard and how to add one.
- The database and migrations: Tables, schema versions, safety copies and how to add a migration.
- Reading ComfyUI: The sync, the read-only gate and the catalog.
- Texts and languages: The catalog of texts, the glossary and adding a language.
- Code words and screen words: Which name in the code is which word on screen.
- Adding a tool for the assistant: Every file a new tool touches.
- Adding a setting: Schema, section, texts and tests.
- Writing a lesson: The lesson format and its test.
- Writing built-in knowledge: Built-in explanations of nodes, types and families.
- Context help ids: How a message in the app links to a wiki page.
- Writing wiki pages: Structure, language and the wiki test.
- Testing: Unit, integration, e2e, the layout walk and the corpus.
- Building from source: Linux step by step; Windows and macOS notes.
- Package formats: What is built, how and what is checked.
- Releasing: The release checklist.
- Contributing: Before a pull request.
- Building and running on Windows: From source on Windows; untested.
- Building and running on macOS: From source on macOS (Apple Silicon and Intel); untested.
- Publishing a clean copy: Why the public repository starts from one commit, and the two scripts that make it.