Support

Use the source channels.

Runebender does not yet have a polished product support structure. For now, support means clear reports, source-first discussion, and careful separation between editor issues, website docs, and broader design questions.

Status	Alpha support map
Audience	Users, contributors, documentation agents
Source	Runebender Core, Xilem, Comfy, Druid, and website links
Stability	Channels may change if the project moves to an organization

Where to go

Channels
Shared core	eliheuer/runebender-core
Native editor	eliheuer/runebender-xilem
Comfy front-end	eliheuer/runebender-comfy
Discussion	Linebender Zulip Runebender channel
Website docs	Use Zulip for stale docs or unclear public-site structure until the website repository is public.

Choose the right report

Use Core issues for headless CLI work, shared editing state, data model, undo, selection, and cross-front-end behavior.
Use Xilem issues for native editor build failures, crashes, UFO behavior, tracing behavior, tools, shortcuts, and format problems.
Use Comfy issues for ComfyUI nodes, Vue/WASM editor behavior, workspace-backed FONT wires, and graph workflows.
Use Zulip for stale docs, broken links, unclear examples, and agent-readable context files until the website repository is public.
Use Zulip for early design discussion, contributor coordination, and questions that are not yet issue-shaped.
Use pull requests when you can make a small, reviewable code or docs change.

Useful report shape

For alpha software, a small precise report is better than a broad complaint.

Include
Context	Source checkout or commit, operating system, Rust version if build-related.
Command	The exact `cargo run` command or app action.
Data	Example UFO path, glyph name, image input, or hyperbezier file if relevant.
Behavior	Expected result, actual result, and whether undo or reopening changed anything.
Scope	Whether it affects local tracing, QuiverAI, normal cubic outlines, hyperbeziers, or docs.

Before asking

Troubleshooting Setup, UFO, tracing, and format checks. Project map Choose Core, Xilem, Comfy, or Druid. Xilem examples Use included UFOs to reproduce native editor behavior. Alpha limits Known instability and caveats. Xilem source map Find likely native editor implementation areas.