Skip to content

Code Goblins on Linux: build, run and installer, with macOS to follow #2366

Open

Description

@fpresta0607

Wanted

The owner asked on 2026-11-11 for Code Goblins to run on more than Windows, with an installer for each system: "we should build a Linux version or Mac version, whatever you think is easier to transition from what we have now. That way, you can have a Linux installer and a Mac installer."

Which first: Linux

Measured on main on 2026-11-11:

  • 2,142 Go files, 492 of them Windows-only by file name (_windows.go), and none written for Linux or macOS.
  • 242 files import Windows system calls.
  • CI already runs 6 jobs on Ubuntu beside 10 on Windows, so part of the code builds and tests on Linux today.

Linux is the easier first step: a Linux runner is already in CI, the binary cross-compiles, and a Linux installer needs no paid signing account. A Mac build needs an Apple developer account, signing and notarization, and Mac runners. Almost everything written for Linux (process groups, pseudo terminals, signals, file locks, paths) serves macOS too, so the Mac build follows as a much smaller second step.

Shape

  1. A written inventory first, in the first pull request: every Windows-only area (the native terminal, job objects and process trees, the credential store, the installer and updater, the janitor's drive handling, hooks and scripts in PowerShell, the desktop window) with what replaces it on Linux, and what is simply not needed there.
  2. The build compiles and its unit tests pass on Linux in CI, with each Windows-only part behind a build tag and a Linux part beside it. One layer per pull request.
  3. A goblin runs end to end on Linux under each supported harness: spawn, send, peek, wake, pause, resume, gate, cleanup.
  4. A Linux installer and updater, and the website's install control offers Linux beside Windows.
  5. macOS is a follow-up issue filed from the inventory, not part of this one.

Constraints

  • Windows behaviour does not change. Every pull request keeps the Windows suite green.
  • No feature is dropped on Linux in silence: the inventory names anything left out and why.
  • No private names, paths or machine details in code, tests or documents.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ops-rootA root issue found while the fleet runs, fixed at its cause

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions