Releases: jasonhnd/loopcoder
Release list
LoopCoder v0.8.1
LoopCoder v0.8.1
Production-path closure for native macOS Apple Silicon.
v0.8.1 connects the orchestration contracts that v0.8.0 published but did not
fully wire into everyday commands. After a post-v0.8.0 product-path audit,
unpinned workers still defaulted to Codex without a durable route decision,
nested children lacked permission-safe routing, waiters and progress hosts were
incomplete, installer custom PATH was broken, and release evidence for real
providers was missing. v0.8.1 closes those gaps on darwin/arm64 only.
Product-path Full GO (packaged gates + live Codex/Claude canaries) passed
on the freeze candidate before tag. Live Apple Developer ID + notarize is
optional and recommended only when you want Gatekeeper-friendly browser
downloads. CLI install via this release uses Sigstore-verified checksums.
| Item | Value |
|---|---|
| Platform | native macOS Apple Silicon (darwin/arm64) only |
| Tracking | #1002 |
| Runbook | docs/reference/v0.8.1-release-runbook.md |
| Go/No-Go gate | docs/reference/v0.8.1-go-no-go.md |
| Capability matrix | docs/reference/v0.8.0-capability-matrix.md |
| Changelog | CHANGELOG.md |
v0.7.0 remains the final legacy multi-platform release. v0.8.0 remains the
prior Darwin arm64 public tag for controlled canary/dev work.
Why this release exists
v0.8.0 shipped important building blocks (inventory, routing contracts,
nested-run records, progress receipts, waiters, budgets). A later audit found
several of those blocks were not connected end to end in the commands
operators actually run:
| Area | v0.8.0 gap | v0.8.1 outcome |
|---|---|---|
| Worker launch | Unpinned dispatch often defaulted to Codex without a durable route decision |
Unpinned workers call route decide, persist authority, then launch the selected adapter/model/effort |
| Verifier | Independent verifier routing incomplete | loopreview persists a verifier route and enforces independence from the worker |
| Delivery | Claim-dispatch of one ready DeliveryRun task incomplete | delivery claim-dispatch is a product path |
| Nested | No permission-safe production nested child routing | Nested children resolve permission-safe routes; orchestrate / unbridged native stay refuse-closed |
| Fallback | Typed provider failures not wired outside worker | Bounded typed fallback after classified Worker failures |
| Wait | Approval / outbox / detached waiters not production-wired | Provider-free loopcoder wait watchers against durable local state |
| Progress hosts | Host visibility contracts incomplete | Codex / Claude / Paseo / generic CLI host contracts |
| Installer | Custom install dir not honored for PATH | LOOPCODER_INSTALL_DIR drives PATH, profile lines, and instructions |
| Release evidence | No protected real-provider canaries / product-path gate | Canaries + go/no-go gate + runbook |
| Live nested canary | Route/inventory/budget gaps blocked live Codex/Claude | Live nested canaries pass on product-path Full GO |
Highlights (operator-facing)
1. Automatic Worker route authority
- Ordinary unpinned
loopcoder dispatchpersists a routing decision before
any provider process starts. - The Worker launches with the selected adapter / model / effort exactly.
- Explicit
--provideris a durable pin with user provenance. - Empty-provider implicit Codex defaults are removed from the prepare path.
no_routereturns exit code 20 with zero provider launches.
2. Independent Verifier route authority
- Unpinned
loopreviewpersists a verifier route decision before launch. - Independence from the configured worker is enforced by policy.
- When no independent read-only verifier is available, the path returns
needs-human rather than silently reusing the worker adapter.
3. DeliveryRun claim-dispatch
delivery claim-dispatchclaims one ready DeliveryRun task under durable
ownership and dispatches it through the product path.- Aligns local DeliveryRun state with worker launch authority.
4. Nested permission-safe child routing
- Nested children resolve a permission-safe route from the immutable child
execution contract before plan persistence and claim/launch. - Mixed read-only / write plans may select different eligible adapters.
- Explicit child or global
--providerpins pass the same nested permission
matrix (read-only vs bounded-write matrix). - Orchestrate permission and unbridged native provider delegation remain
refuse-closed. - Route receipts (decision id, adapter, model, outcome, reason) appear on child
results for audit. - Live release canaries exercise this path with real Codex and Claude CLIs.
5. Typed provider failure → bounded fallback
- After Worker classifies a provider failure,
dispatchand
delivery claim-dispatchcan callrouting.ApplyTypedProviderFailurewhen a
route decision exists. - Pins and needs-human classes stay fail-closed.
- Auto-eligible classes may persist a bounded successor without relaunching
a provider in-process.
6. Production wait wiring
loopcoder waitships provider-free watchers:approvaloutboxdetached-workerquota-reset(still available)
- Restartable file checkpoints; zero provider launches on the wait path.
- GitHub CI waiting remains on the existing orchestration path.
7. Host progress visibility
- Negotiated foreground sinks for Codex, Claude, Paseo, and generic CLI.
- Worker progress delivery annotates the selected host.
- Unknown hosts degrade to generic.
- Active delivery still never uses a model to “poll progress”.
8. Installer custom directory PATH
LOOPCODER_INSTALL_DIRis used for PATH detection, shell profile lines, and
printed instructions (quoted for spaces).- Re-runs stay idempotent.
LOOPCODER_NO_MODIFY_PATH=1prints guidance without editing profiles.- Relative install directories are rejected.
9. Release evidence harnesses
- Blocking Codex/Claude canaries:
scripts/release-provider-canary.sh
(fixture + live; live requiresLOOPCODER_REAL_PROVIDER_CANARY=1). - Non-blocking Grok/Antigravity canaries (
blocking:false; soft
not_availableoutcomes). - Product-path go/no-go gate:
scripts/v081-product-path-gate.sh→
loopcoder.v081_go_no_go.v1JSON + human report. - Apple sign/notarize harness: dry-run always; live opt-in
(APPLE_SIGN=1+ Developer ID + notary profile). - Operator runbook: freeze → Full GO → publish.
10. Live nested canary reliability (pre-tag fixes)
Fixes required so live Codex/Claude nested canaries actually route and launch
on a real machine (not just fixtures):
- Valid canary plan run IDs (
state.IsRunIDshapes) and fixture-repo
core.hooksPath=/dev/null. - Nested route authority (
router/ user pin provenance), display-name model
pin resolution to opaquemcap_*inventory IDs, nested budget authority
seeding, and no hard pin of unsupported deep/fast invocation profiles. - Inventory: promote
usable_for_invocation=yeswhen auth readiness is ready;
adapter-declared models available for routing; passUSER/LOGNAMEinto
provider auth probes (required for Claudeauth status --json). - Routing: derive availability scores when none are persisted; low-risk paths
may proceed without uncollected quota/budget telemetry. - Product-path Full GO does not require live Apple Developer ID.
Platform support
| Host | v0.8.1 |
|---|---|
native macOS Apple Silicon (darwin/arm64) |
Supported |
| Windows / Linux / WSL / containers as runtime | Unsupported (use v0.7.0) |
| Intel macOS / Rosetta amd64 | Unsupported (use v0.7.0) |
Unsupported hosts fail closed with exit code 78 /
ErrUnsupportedPlatform before network, credentials, provider launch, or
storage mutation.
Published archive shape:
loopcoder_0.8.1_darwin_arm64.tar.gz
SHA256SUMS
SHA256SUMS.sigstore
Install
Release installer (recommended)
curl -fsSL https://raw.githubusercontent.com/jasonhnd/loopcoder/main/scripts/install.sh | sh -s -- --version 0.8.1
loopcoder version
loopcoder doctorCustom directory:
LOOPCODER_INSTALL_DIR="$HOME/tools/loopcoder" \
curl -fsSL https://raw.githubusercontent.com/jasonhnd/loopcoder/main/scripts/install.sh | sh -s -- --version 0.8.1Guidance only (do not edit shell profiles):
LOOPCODER_NO_MODIFY_PATH=1 \
curl -fsSL https://raw.githubusercontent.com/jasonhnd/loopcoder/main/scripts/install.sh | sh -s -- --version 0.8.1Go install (supported host with Go toolchain)
go install github.com/jasonhnd/loopcoder/cmd/loopcoder@v0.8.1
loopcoder versionFirst consumer repository
loopcoder init --repo .
loopcoder skill install --repo .
loopcoder projects register --repo .
loopcoder doctor --repo .
loopcoder report --repo .
# then: /loopcoder <your need> (or dispatch / tick / loopreview)Prerequisites on PATH
git- authenticated
gh - at least one registered provider CLI (
codexdefault worker;claudefor
independent verification; optionalgrok,agy/ antigravity)
Provider registration is not proof of authentication, usable capacity, or
safe role support. Run loopcoder providers refresh and consult the capability
matrix before unattended dispatch.
Upgrade from v0.7.0 / v0.8.0
On native Darwin arm64 only:
loopcoder upgrade --version 0.8.1
loopcoder version
loopcoder migrate storage --format json
loopcoder migrate storage --apply --format json
loopcoder skill install --repo .
loopcoder projects register --repo .
loopcoder doctor --repo . --format json
- Storage migrate is plan-only unless `--appl...
v0.8.0
LoopCoder v0.8.0
v0.8.0 is the public native Darwin arm64 release. It includes multi-provider,
routing, nested-run, progress, waiter, detached-execution, and migration
building blocks. Its exact archive passed the documented publication,
integrity, deterministic smoke, and v0.7 migration gates. A later product-path
audit found that several orchestration building blocks are not connected end
to end or proven with real providers, so use v0.8.0 for controlled canary and
development work rather than unattended production orchestration.
The binding distinction between implemented code, reachable commands,
deterministic coverage, real-provider evidence, and production support is in
the
v0.8.0 capability and support matrix.
Platform Support
LoopCoder v0.8.0 supports native macOS Apple Silicon (darwin/arm64) only.
Windows, Linux/Ubuntu, WSL, containers used as a LoopCoder runtime, Intel
macOS, and Rosetta/amd64 macOS are unsupported and receive no v0.8 artifact,
native CI, smoke, or compatibility commitment. v0.7.0 remains the final legacy
multi-platform release for those users.
The release publishes one binary archive:
loopcoder_0.8.0_darwin_arm64.tar.gz
SHA256SUMS and its Sigstore bundle accompany that archive. This verifies
checksum provenance and archive integrity. The v0.8.0 Mach-O is not Apple
Developer ID signed or notarized, so this release does not provide Gatekeeper
trust.
Highlights
- Provider intelligence infrastructure: bounded provider/account
discovery, dynamic model capability catalogs, supported quota telemetry,
optional CodexBar evidence, and a conservative local usage ledger. Inventory
is diagnostic evidence, not proof of authentication or usable capacity. - Routing contracts: deterministic task requirements, capability
eligibility, quota/reset-aware scoring, typed fallback, independent-verifier
policy, and hierarchical budget records exist. Ordinary unpinned dispatch
still defaults directly to Codex; automatic routing is not supported. - Grok integration: the
grokworker provider, dynamic model inventory,
bounded ACP billing when advertised and allowed, and native-agent capability
probing without auto-install, auto-update, or login behavior. - Nested-run infrastructure: durable parent/child registrations, depth,
fan-out, concurrency, permission, budget, cancellation, and one-writer
records support deterministic fixtures. No real-provider nested execution
mode is supported in v0.8.0. - Durable execution: non-interactive work defaults to detached supervision;
provider PID, process group, birth identity, owner, and generation fence
ps,status,kill, recovery, and Darwin guardian behavior. - Durable progress without model polling: five-minute receipt, outbox, and
restartable waiter components persist local evidence without provider calls.
The local CI waiter is connected; unsolicited host delivery and the other
production waiter integrations are not supported. - Bounded orchestration cost: per-run calls, tokens when known, waiting,
recovery, delivery, and verification overhead are measured and gated. - Auditable migration:
migrate storageplans without side effects,
verifies an owner-only v0.7 backup, atomically applies schema 9 through 30,
and reports stable rollback limitations.
Upgrade From v0.7.0
On native Darwin arm64:
loopcoder upgrade --version 0.8.0
loopcoder version
loopcoder migrate storage --format json
loopcoder migrate storage --apply --format json
loopcoder skill install --repo .
loopcoder projects register --repo .
loopcoder doctor --repo . --format json
The storage command is plan-only unless --apply is present. Stop all
LoopCoder processes before migration or rollback. The apply path creates and
verifies one owner-only schema-9 backup before the write transaction; replay on
schema 30 returns no-op.
Backup And Rollback
Do not point a v0.7.0 binary at the migrated schema-30 database. To roll back:
- stop every LoopCoder process;
- retain the migrated database as evidence;
- copy, never move or mutate, the verified migration backup into an offline
rollback home; - select the published v0.7.0 binary; and
- run
loopcoder doctor --repo .against the restored home.
Rollback discards v0.8-only state created after migration. The exact procedure
and stable limitation codes are in
docs/reference/storage-migration.md.
Completed Publication Gates
The immutable v0.8.0 tag resolves to
bd382a5bcc7e20ae29e239b43d896a1b25796d59. Publication completed after:
- required
verify,test,race, andsecuritychecks; - the complete repository race suite in the release build;
- signed checksum and staged-archive identity verification;
- fresh install, v0.7 upgrade, migration, rollback, self-bootstrap, and release
smoke on pinned Darwin arm64; - zero open release blockers;
- the protected
release-publicationenvironment approval; and - a completed
v0.8.0 go/no-go report.
Those gates establish the published artifact's identity, integrity, migration
behavior, and deterministic release smoke. They did not include protected
exact-artifact Codex/Claude product-path canaries or Apple notarization, and do
not override the capability matrix.
Known Limitations
-
Automatic Worker routing, routed Verifier independence, typed fallback, and
quota-reset waiting are not connected product paths. Explicitly pinned
provider use is canary-only. -
The accepted nested read-only path does not enforce mutation-free behavior
inside the Worker adapter. Production-provider write and orchestrate modes
are refused. Do not use real providers withnested runin v0.8.0. -
Durable receipts do not prove unsolicited live visibility in the initiating
host. Approval, outbox, and detached-terminal waiters are not fully wired. -
Protected exact-v0.8.0 Codex and Claude canaries are absent. Grok and
Antigravity have deterministic adapter coverage but no release-gated live
canary. -
The binary is not Apple Developer ID signed or notarized. The installer can
place a binary in a custom directory, but its PATH/profile guidance assumes
the default directory. -
Exact quota and reset behavior is available only when a supported, fresh
machine-readable source exposes it. Unavailable evidence is not guessed. -
Antigravity has no verified read-only mode and therefore cannot run
loopreview; directgeminiremains experimental. -
Grok model and billing evidence depends on capabilities exposed by the local
Grok CLI and explicit network permission. -
Detached supervision is machine-local and does not replace the human
conductor or production publication gate.
v0.7.0
loopcoder v0.7.0
v0.7.0 moves loopcoder's local runtime from repo-only files toward a
machine-local runtime model while preserving the local-only evidence boundary.
The release was published on 2026-07-11 with signed assets for v0.7.0,
verified checksums, passing release smoke, and a completed GO go/no-go report.
Highlights
- Machine-local runtime storage: project identity, imported run records, and
report query data are backed by$LOOPCODER_HOME/data/loopcoder.db. - Project registry:
loopcoder projects register|show|list|removemanages
stable project identities across multiple local checkouts without deleting run
history. - Explicit local-state migration:
loopcoder migrate local-state --repo . --dry-runpreviews v0.6.x repo-local.loopcoder/imports; the non-dry-run
path imports attempts, events, reports, recovery briefs, and relay records
without deleting source files. - Provider compatibility visibility:
doctor --format jsonexposes the
host profile andprovider_compatibility[]matrix so supported,
experimental, and unsupported worker/verifier/nested modes are auditable. - Nested run observability:
status --format jsonand
report --run <id> --format jsoninclude arun_treeobject for parent and
child runs. - Self-bootstrap acceptance:
scripts/self-bootstrap-smoke.ps1verifies the
loopcoder checkout, registry, database location, provider compatibility
visibility, and parent/child run-tree JSON as part of the release gate. - Release-gated publication: v0.7.0 assets are staged in a draft release,
smoked on Ubuntu, macOS, and Windows, and published only after the
release-publicationenvironment approval.
Added
loopcoder projects register|list|show|removefor the machine-local project
registry.loopcoder migrate local-statefor explicit v0.6.x repo-local state import.loopcoder nested runfor bounded v1 child-plan execution.status --format jsonandreport --run <id> --format jsonrun-tree
observability.- Provider/host compatibility diagnostics in
doctor --format json. - Unix-like owner-only permissions for
$LOOPCODER_HOME,data/, the SQLite
database, and SQLite sidecars.
Changed
- New runtime indexes for registered projects move to
$LOOPCODER_HOME/data/loopcoder.db; repo-local.loopcoder/remains
readable compatibility state during migration. doctor --fixcan repair Unix storage modes and eligible local compatibility
surfaces, but stays local and explicit.- Default reporter text output is the compact receipt. Use
--verbosefor
canonical local records and--format jsonfor machine-readable output. - Release automation creates a draft release before platform smoke and leaves a
failed candidate as draft evidence instead of publishing it.
Fixed
- Git remote credentials are sanitized before registry persistence or output.
- Project identity comparison handles macOS alias/canonical path differences.
- Nested child run IDs, terminal mirror events, required skipped children, and
project-list JSON stability were corrected before the release gate. - Release smoke handles multi-line PowerShell output when checking the
already-latest upgrade path.
Compatibility
- v0.7.0 is the stable install target published with signed assets on
2026-07-11. Upgrade from v0.6.1 withloopcoder upgrade --version 0.7.0. - Existing
.loopcoder/repo-local files are not moved or deleted by upgrade
or migration. They remain a compatibility fallback during the transition. - The SQLite database is machine-local, not a cloud sync mechanism and not a
repository-visible artifact. audit --format bothis removed. Use--format textor--format json.- Windows does not enforce owner-only DACL hardening for v0.7.0 storage paths;
doctorreports that limitation explicitly.
Upgrade
Upgrade from the customer-ready v0.6.1 bridge:
loopcoder upgrade --version 0.7.0
loopcoder version
loopcoder skill install --repo .
loopcoder projects register --repo .
loopcoder migrate local-state --repo . --dry-run
loopcoder doctor --repo . --format json
Run the non-dry-run migration only after reviewing the dry-run output:
loopcoder migrate local-state --repo .
The migration copies compatible local records into the machine-local store. It
does not delete repo-local .loopcoder/ history, edit tracked files, mutate
GitHub, flush relay records, or choose providers.
Backup and Rollback
Back up v0.7.0 local runtime state by copying
$LOOPCODER_HOME/data/loopcoder.db plus $LOOPCODER_HOME/projects/,
$LOOPCODER_HOME/logs/, and $LOOPCODER_HOME/tmp/ when those directories are
present and no loopcoder command is running.
Rollback is binary selection plus local-state retention:
loopcoder upgrade --version 0.6.1
loopcoder version
loopcoder skill install --repo .
loopcoder doctor --repo .
Keep or back up $LOOPCODER_HOME before deleting anything. Do not delete
repo-local .loopcoder/ history unless an operator explicitly chooses to; it
is the compatibility fallback for pre-v0.7.0 local records.
Known Limitations
- Nested orchestration is bounded and plan-driven. Provider-native sub-agent
features are not authoritative orchestration and cannot create untracked
children outside loopcoder. test-subprocessis reserved for deterministic local and release smoke
tests.- Windows storage ACL hardening remains a documented limitation for a later
release. - Pre-existing flaky test #765 is not release-blocking and is tracked as a
deferred test-only flake.
Release Verification
The release reached GO with these checks complete:
- Release: https://github.com/jasonhnd/loopcoder/releases/tag/v0.7.0,
published 2026-07-11T10:32:49Z, latest, 8 assets, draft=false,
prerelease=false. - Tag/commit: v0.7.0 =
9129dd80fb67d2c395269771d7de8643f2868578; binary version stamp verified:
version=0.7.0 commit=9129dd80fb67d2c395269771d7de8643f2868578 go=go1.26.5. - Staged release run:
https://github.com/jasonhnd/loopcoder/actions/runs/29148964764, with 6
builds, sign, draft, native smoke ubuntu/macos/windows all success, and
publish success after required-reviewer approval (jasonhnd). - Integrated main CI on the tagged SHA:
https://github.com/jasonhnd/loopcoder/actions/runs/29148868926 (8/8
success). - Independent public verification passed:
scripts/release-smoke.ps1 -Version v0.7.0 -PreviousVersion 0.6.1, including
the real v0.6.1 -> v0.7.0 upgrade, signed checksum verification against
identity
https://github.com/jasonhnd/loopcoder/.github/workflows/release.yml@refs/tags/v0.7.0,
issuerhttps://token.actions.githubusercontent.com, and SHA256 match
c510e709d8c95e442261990fd309228aa151ce0bb32b6a2026476685af3f61be. - Publication controls were applied and verified on 2026-07-11: main branch
protection (8 required checks, strict, enforce_admins, 1 review) and
release-publicationrequired reviewer jasonhnd.
Notes
- v0.7.0 is the published install target as of 2026-07-11.
- Local-only report, relay, run, and database records remain local-only. Do not
copy reporter blocks or raw local records into PR bodies, issue comments,
merge messages, commits, examples, fixtures, or tracked docs. - Rollback is binary selection plus project-local cleanup: select a prior
released binary such as v0.6.1, keep or back up$LOOPCODER_HOME, and leave
repo-local.loopcoder/history untouched unless an operator explicitly
removes it.
v0.6.1
loopcoder v0.6.1
v0.6.1 is the customer-ready bridge for the public 0.6 line. The latest public
release before this bridge was v0.5.4; customers should install or upgrade to
v0.6.1, not to a nonexistent public v0.6.0 release.
This release packages the 0.6 capabilities into an operable first-run customer
flow: model/depth discovery, Antigravity worker support, reporter output,
upgrade/migration compatibility, skill install, read-only doctor, local run
status, report querying, relay gates, loopreview, audit, state branch, lease,
and process watchdog behavior.
Install
Unix-like systems:
curl -fsSL https://raw.githubusercontent.com/jasonhnd/loopcoder/main/scripts/install.sh | sh -s -- --version 0.6.1
Windows PowerShell:
$env:LOOPCODER_VERSION = "0.6.1"
irm https://raw.githubusercontent.com/jasonhnd/loopcoder/main/scripts/install.ps1 | iex
The install scripts verify signed SHA256SUMS with cosign before trusting
release checksums.
Upgrade from v0.5.4 or older 0.5.x
loopcoder upgrade --version 0.6.1
loopcoder version
loopcoder skill install --repo .
loopcoder doctor --repo .
loopcoder upgrade --version 0.6.1 selects the machine-level binary and
refreshes the global bundled skill. Each project still needs
loopcoder skill install --repo <repo> to refresh project hook settings,
.loopcoder/conductor-workspace, and local .git/info/exclude protection for
.loopcoder/. Then run loopcoder doctor --repo <repo> to confirm readiness.
After v0.6.1 is selected, re-running loopcoder upgrade --version 0.6.1 should
report that the selected binary is already latest.
Customer quickstart
From a repository root:
loopcoder version
loopcoder init --repo .
loopcoder skill install --repo .
loopcoder doctor --repo .
loopcoder report --repo .
Then drive work from a conductor session:
/loopcoder <your need>
New init scaffolds default to adapters.gate: human-merge; pass
loopcoder init --repo . --gate auto only when the project should opt into
automatic production promotion.
Command side effects
| Command | Side effects |
|---|---|
loopcoder init --repo . |
Writes .delivery.yml, ROADMAP.md, GitHub labels, and local .git/info/exclude protection for .loopcoder/. |
loopcoder skill install --repo . |
Writes or refreshes global skill files, project hook settings, .loopcoder/conductor-workspace, and local .git/info/exclude protection. |
loopcoder doctor --repo . |
Read-only diagnostics; --format json emits machine-readable checks. |
loopcoder report --repo . |
Read-only local report query. |
loopcoder status --repo . |
Read-only local run status. |
loopcoder state push --repo . |
Explicitly writes run summaries to the dedicated state branch. |
loopcoder promote --repo . |
May change the configured production branch, subject to adapters.gate and the human command. |
What changed
loopcoder init --repo <path>and--gate human-merge|auto; new scaffolds
default tohuman-merge.initandskill install --repoprotect repo-local.loopcoder/through
.git/info/excludewithout touching tracked.gitignore.loopcoder doctor --format text|jsonincludes local-state, reportquery,
installed-skill, hook, provider, and migration checks.loopcoder report --format jsonnow includes both top-levelreportsand
richerrecordsentries withreport,source,run_id, andpath.- README and usage docs list every registered command, including
report,
state,lease,ps, andkill. - Pretty report docs now match the renderer's combined provider line, such as
OpenAI Codex / codex.
Local state boundary
.loopcoder/ is repo-local machine state for runs, relay ledgers, recovery,
status, and report queries. It must not be committed to normal business
branches. loopcoder state push is the explicit state-branch publishing path.
A machine can serve many projects: each project owns its own .delivery.yml
and .loopcoder/, while the machine-level binary and bundled skill live under
the user's machine-level loopcoder/agent directories.
v0.6.1 introduces no SQLite database, global project registry, project alias
map, or native sub-agent scheduler.
Compatibility
The 0.5.x to 0.6.x reporter compatibility window remains intact. Legacy inputs
and aliases are still accepted, while new output and new documentation use the
reporter terminology.
v0.5.4
Automated release for v0.5.4. SHA256SUMS is signed with cosign keyless identity https://github.com/jasonhnd/loopcoder/.github/workflows/release.yml@refs/tags/v0.5.4 and OIDC issuer https://token.actions.githubusercontent.com.
v0.5.3
Automated release for v0.5.3. SHA256SUMS is signed with cosign keyless identity https://github.com/jasonhnd/loopcoder/.github/workflows/release.yml@refs/tags/v0.5.3 and OIDC issuer https://token.actions.githubusercontent.com.
v0.5.2
Automated release for v0.5.2. SHA256SUMS is signed with cosign keyless identity https://github.com/jasonhnd/loopcoder/.github/workflows/release.yml@refs/tags/v0.5.2 and OIDC issuer https://token.actions.githubusercontent.com.
v0.5.1
Automated release for v0.5.1. SHA256SUMS is signed with cosign keyless identity https://github.com/jasonhnd/loopcoder/.github/workflows/release.yml@refs/tags/v0.5.1 and OIDC issuer https://token.actions.githubusercontent.com.