Compatibility and data

Check supported files, published platforms, data boundaries and current limitations.

Linux AMD64, Linux ARM64, Windows x64 · Release 0.1.5

On this page

Published platform

The prepared 0.1.6 client targets Windows 11 x64 and Ubuntu 24.04/26.04 AMD64/ARM64, using the matching native Windows installer or Linux .deb. This is not a publication announcement: availability and exact version are authoritative on the download page, not implied by a demonstration recording. The previous 0.1.5 portable Linux payload targets Ubuntu 26.04; its ARM64 build requires glibc 2.43 and does not support Ubuntu 24.04. Do not apply that older payload's requirements or installer commands to a 0.1.6 .deb.

Always consult Downloads and Release notes for current package availability. Do not subscribe for an unavailable platform. No browser edition or macOS installer is offered by this release.

Files and project compatibility

Native project formats include .kicad_pro, .kicad_sch and .kicad_pcb. Local symbol and footprint libraries are part of a reproducible project. Opening older files may trigger conversion; back up before saving and do not assume older software can reopen the converted file.

See Projects and libraries for local paths and library setup. Compatibility with a file format does not imply affiliation with its upstream project. Open-source attribution and corresponding source are available in Notices and the download page.

What is local and what is sent

Project editors operate on local files. An AI request sends the context needed for the task to its configured provider through the applicable backend route. Do not describe AI assistance as entirely offline. Select only relevant context and avoid secrets or unrelated private files.

API keys belong in the native credential dialog and backend storage, not the browser, conversation or project. Private developer Codex accounts are not distributed to customers. BYOK uses your own provider account and billing.

Read Data handling and the Privacy policy for the distinction between project context, account information, support requests and service records.

Engineering limits

Plans, explanations, previews, ERC and DRC are aids to review—not certification, design approval or proof of physical performance. Validate datasheet constraints, component selection, power, thermal behavior, safety, manufacturability and regulatory requirements independently.

Object-level comparison supports particular native structures; unsupported or uncertain matches must remain visible. A text diff alone cannot establish correct topology. Exports need review against their exact source revision and your manufacturer's requirements.

Early-access expectations

Keep recoverable backups and start on a disposable project. Tools can fail, provider availability can change and a task can end without a usable candidate. A stopped task or a passing adapter test is not evidence of completed engineering work.

The demo and tutorial state their source and limitations. We do not present retained failed validations as success, or existing demonstration boards as generated designs. Report a reproducible issue through Support with safe identifiers and the step that failed.

Search documentation

Type to search the TraceForge guides.