using ironwood

Engines and storage with Companion

Install and manage desktop engines, choose an archive, and follow automatic imports.

Install an engine

Connect Companion using the Windows setup guide. Open Settings → Engine settings… and choose the + button next to the engine list.

Auto-install shows packages supported by the selected Companion. Choose a package to download and install. Companion downloads directly from the original publisher, checks the package, and registers the engine. Downloads can continue after closing the window. Engines and any models are stored on the Companion computer.

Manual is for engines you already have. Keep the executable and its supporting files together under Companion’s Engines folder. Choose the folder and executable, review the detected engine name, then choose Save engine. Expand the arguments section only if the engine needs additional launch arguments.

Windows x64 Auto-install engines

The catalog depends on your Companion version. Open Auto-install to see which packages your connected Companion offers.

EngineStandard chessChess960
Stockfish 19YesYes
Weiss 2.0YesYes
Lc0 CPU 0.32.1YesYes
Arasan 26.1YesNo
Laser 1.7YesNo
Supernova 2.4YesNo

Chess960 limitations

  • For local play against AI, select a Chess960-compatible opponent before choosing Chess960 under Starting position. A custom Chess960 FEN also requires a compatible opponent.
  • Position and full-game analysis of Chess960 games require a compatible engine. Built-in browser Stockfish supports Chess960 without Companion.
  • Manually added engines qualify if they advertise UCI_Chess960 when Companion connects to them.

Manage an installed engine

Select the engine in Engine settings, then choose the sliders icon, Manage engines. This opens the selected engine; you do not need to choose it again. Change its display name, executable, or launch arguments, then save and reselect the engine to start a new session.

The Engine options tab controls the engine’s advertised playing and analysis options. Play, Realtime Analysis, and Full game Analysis control the work for those uses. Managing the installation does not replace these controls.

Renaming an engine changes its display label and keeps its registration identity. Remove from Companion… removes that registration. For packages installed by Companion, you can also choose to delete its installed files. Manually added engine files are kept. Saved games and training history are kept; a profile using a removed engine cannot start until that engine is restored.

Import into an archive

Open Game library → Import… and choose the named Companion in the location list. Choose a supported file with Browse…, drag it onto the app, or paste PGN. Review the selection and destination before importing. Choose Browser instead if the collection should stay in this browser.

For Scid databases, clearing Through game returns the range to the database’s last game. Use the full matching set of Scid files, or a supported archive containing that set. Scid import reads the source without changing it.

Use the Import folder

In Companion’s status window, choose Import to open its watched folder. Place a PGN, ZIP, or 7z file there. ZIP and 7z archives can contain PGN files or matching Scid database files. For an uncompressed Scid database, keep all matching files together. The original source is read locally.

In Ironwood’s Import window, select that Companion to see its folder-import progress. Counts distinguish read, saved, duplicate, short, deleted, and failed games. Speed and estimated time remaining describe the import; opening-index progress is a separate task and can trail behind saved games. Estimates vary as the workload changes.

The queue reports when it is waiting, retrying, stopped, complete, or needs attention. Use the Reports folder for the import report. On restart, supported folder imports resume from the last saved batch rather than treating earlier committed batches as new work.

Back up the right location

Browser backups and Companion archives are separate. Check the selected location before exporting or deleting games. Export games you need in PGN for interchange. For a complete Companion data-folder backup, quit Companion before copying the data folder so the archive is not changing during the copy. Keep engine models and configuration with the backup if you need a complete recovery.

See Companion troubleshooting for connection and import errors.

Switch engines

Use the engine list in Settings → Engine settings…, or the selector beside Analyze, to choose a Companion engine. Your choice appears immediately while its capabilities are prepared. Returning to a previously discovered engine in the same browser session skips the discovery probe. Refreshing installed engines, or changing connections or credentials, clears that cache. First-time discovery and starting the actual engine can still take time.

To compare results already saved for a game, use Saved Analysis instead of changing the engine for the next run.

Unified game management

The old Your game archive window has been retired. Use Game library → Saved games… for collections, browsing, metadata, copies, moves, exports and deletion. Choose Browser or a named Companion there. Use Game library → Backup and Restore… for backups, Settings → Companion connection… for connections, and the Import Games window for folder-import progress.

In Browser Saved Games, copy and move controls use your Companion’s saved name. If several Companions are configured, open Copy to… or Move to… and choose a named destination from the submenu; disconnected destinations are disabled. These controls are available for selected games above the list and in each saved game’s ☰ menu, including its larger preview. See Saved games and backups.

← Back to all help