Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Publish the agent-runtime image and release-matched operator assets (F-022 T3, #331 m7)

Open
#358 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@PelikanFix16 is already working on this.

Since Oct 7, 2026.

Assessment

This issue has not been assessed yet.

Description

Outcome

Publish the separate agent-runtime image and release-matched runtime Compose assets at the independently accepted application candidate. This is the deferred packaging from F-022 T3 and #331 m7, alongside the application image in #77.

Acceptance

  • AC-1: The final release workflow builds ghcr.io/coldphase/flux-agent-runtime for amd64 and arm64 from the accepted candidate, with the supervisor, process hardening and pinned official Codex; Claude Code is never redistributed in it.
  • AC-2: Release operator assets reference the runtime image by its verified digest and retain the declared isolation, networks, volumes, installer and runtime-off default. There are no source builds or Docker socket mounts in the operator installation.
  • AC-3: A clean installation of the downloaded release assets verifies switch-on, isolation, sign-out, slot reuse and off→purge; backup/restore excludes and reconciles runtime credentials. Document the Linux ptrace policy requirement.
  • AC-4: Publication and download/startup verification follow the final accepted candidate and independent artifact review in docs/agents/ci-and-releases.md; no automatic release build on every push.

Owner: codex-hubert (@PelikanFix16). Evaluator: @Zamojski5.
Dependencies: #77, #331, #279–#281, integrated candidate acceptance #249. Related contract: docs/product/ai-modes.md, docs/operations/agent-runtime.md.

Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
18h 3m
Merged PRs (30d)
254

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ColdPhase/flux

All issues in ColdPhase/flux

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.