coleam00/Archon · warning

Warning: ${warning}

Error message

  Warning: ${warning}

What it means

The generic warning printer in `isolationCompleteCommand` (packages/cli/src/commands/isolation.ts:419) that surfaces non-fatal cleanup warnings collected in `result.warnings` after worktree/branch teardown. The completion succeeded (possibly partially), and each warning string describes a step that could not be fully cleaned up, e.g. remote branch deletion failure.

Source

Thrown at packages/cli/src/commands/isolation.ts:419

        console.error(`  Blocked: ${branch}`);
        for (const blocker of blockers) {
          console.error(`    ✗ ${blocker}`);
        }
        console.error('  Use --force to override.');
        failed++;
        continue;
      }
    }

    try {
      const result: RemoveEnvironmentResult = await removeEnvironment(env.id, {
        force: options.force,
        deleteRemoteBranch: options.deleteRemote ?? true,
      });

      // Surface warnings from partial cleanup
      for (const warning of result.warnings) {
        console.warn(`  Warning: ${warning}`);
      }

      if (result.skippedReason) {
        console.error(`  Blocked: ${branch} — ${result.skippedReason}`);
        if (result.skippedReason === 'has uncommitted changes') {
          console.error('    Use --force to override.');
        }
        failed++;
      } else if (!result.worktreeRemoved) {
        const parts: string[] = [];
        if (result.branchDeleted) parts.push('branch deleted');
        parts.push('DB updated');
        console.error(
          `  Partial: ${branch} — worktree was not removed from disk (${parts.join(', ')})`
        );
        for (const warning of result.warnings) {
          console.error(`    ⚠ ${warning}`);
        }

View on GitHub (pinned to 0773b97458)

Solutions

1. Read the specific warning text printed — it names the cleanup step that partially failed.
2. If the remote branch delete failed, delete it manually: `git push origin --delete <branch>`.
3. Re-run `archon isolation complete <branch>` after fixing the cause; it should now report no warnings.
4. If the warning is benign (already-deleted remote branch), no action is needed.

// Pre-check remote branch existence so the warning is expected
git ls-remote --heads origin <branch>

const result = await completeBranch({ branch, deleteRemoteBranch: true });
for (const w of result.warnings) {
  console.error(`cleanup warning: ${w}`); // decide per-warning whether it blocks your workflow
}

When it happens

Trigger: Calling `archon isolation complete <branch>` where the underlying complete result contains warnings — typically when `deleteRemoteBranch` is true but the remote branch delete fails, or a partial cleanup step errors without blocking the result.

Common situations: Remote branch already deleted on the GitHub side but still present locally; missing/failed `gh` auth for remote operations; branch protection or permissions blocking remote deletion.

Related errors

• Failed to create worktree for PR #${prNumber}: ${err.message
• Cannot resume: Not in a git repository. Either run from a gi
• Not in a git repository. Run archon workflow install from wi
• Status: Failed - ${err.message}
• Error processing codebase: ${err.message}

AI-assisted analysis of coleam00/Archon@0773b97458 (2026-09-01). Data as JSON: /api/errors/83051f89ba0a075c. Report an issue: GitHub.