Skip to content
Effloow
← Back to article
EFFLOOW LAB LAB-RUN

Archon V2 Ai Coding Agent Harness Builder 2026

Evidence notes document the bounded local or source-based checks behind an Effloow article. They are not product endorsements, legal advice, or benchmark claims.

Date: 2026-05-19 Track: sandbox-poc Slug: archon-v2-ai-coding-agent-harness-builder-2026

Goal

Evaluate whether Archon's current TypeScript workflow-engine direction is useful for deterministic coding-agent harnesses. The sandbox focused on local, credential-free checks only:

  • Clone the public repository.
  • Inspect bundled workflows and command definitions.
  • Create a minimal .archon/workflows/*.yaml file.
  • Validate dependency ordering and parallel review fan-out with a local script.
  • Attempt the documented Docker CLI path without providing credentials.

Environment

Host: macOS
Working directory: /tmp/effloow-archon-poc-2026-05-19
Node: v25.9.0
npm: 11.12.1
git: git version 2.50.1 (Apple Git-155)
bun: not installed
Docker: Docker version 29.2.0, build 0b9d198

Commands and Outputs

1. Prepare isolated sandbox

SANDBOX=/tmp/effloow-archon-poc-2026-05-19
rm -rf "$SANDBOX"
mkdir -p "$SANDBOX"
cd "$SANDBOX"

2. Clone the current Archon repo

git clone --depth 1 https://github.com/coleam00/Archon.git archon-src
cd archon-src
git rev-parse --short HEAD

Output:

45bc5e5

3. Inspect package metadata

node -e "const p=require('./package.json'); console.log(JSON.stringify({name:p.name,version:p.version,type:p.type,scripts:p.scripts}, null, 2))"

Relevant output:

{
  "name": "archon",
  "version": "0.3.12",
  "type": "module",
  "scripts": {
    "cli": "bun --cwd packages/cli src/cli.ts",
    "validate": "bun run check:bundled && bun run check:bundled-skill && bun run type-check && bun run lint --max-warnings 0 && bun run format:check && bun run test"
  }
}

Observation: the current repository is TypeScript/Bun-based and reports package version 0.3.12. The backlog title uses "v2" as a rewrite-era label, but the article should not claim the package version is literally v2.

4. Inspect bundled workflow and command count

find .archon/workflows -type f \( -name '*.yaml' -o -name '*.yml' \) | wc -l
find .archon/commands/defaults -type f | wc -l
find .archon/workflows -type f | sort | head -n 20

Output:

workflow files=      37
default command files=      36
.archon/workflows/archon-test-pi.yaml
.archon/workflows/defaults/archon-adversarial-dev.yaml
.archon/workflows/defaults/archon-architect.yaml
.archon/workflows/defaults/archon-assist.yaml
.archon/workflows/defaults/archon-comprehensive-pr-review.yaml
.archon/workflows/defaults/archon-create-issue.yaml
.archon/workflows/defaults/archon-feature-development.yaml
.archon/workflows/defaults/archon-fix-github-issue.yaml
.archon/workflows/defaults/archon-idea-to-pr.yaml
.archon/workflows/defaults/archon-interactive-prd.yaml
.archon/workflows/defaults/archon-issue-review-full.yaml
.archon/workflows/defaults/archon-piv-loop.yaml
.archon/workflows/defaults/archon-plan-to-pr.yaml
.archon/workflows/defaults/archon-ralph-dag.yaml
.archon/workflows/defaults/archon-refactor-safely.yaml
.archon/workflows/defaults/archon-remotion-generate.yaml
.archon/workflows/defaults/archon-resolve-conflicts.yaml
.archon/workflows/defaults/archon-smart-pr-review.yaml
.archon/workflows/defaults/archon-test-loop-dag.yaml
.archon/workflows/defaults/archon-validate-pr.yaml

5. Create a minimal sandbox workflow

File: /tmp/effloow-archon-poc-2026-05-19/sample-repo/.archon/workflows/effloow-sandbox.yaml

name: effloow-sandbox
description: Minimal deterministic review workflow for an article-code sandbox
nodes:
  - id: inspect
    bash: "printf 'inspect ok\n'"

  - id: plan
    prompt: "Create a short implementation plan from the inspection output."
    depends_on: [inspect]

  - id: validate
    bash: "printf 'validate ok\n'"
    depends_on: [plan]

  - id: review-copy
    prompt: "Review the output for unsupported claims."
    depends_on: [validate]

  - id: review-risk
    prompt: "Review the output for operational risks."
    depends_on: [validate]

  - id: summarize
    prompt: "Summarize the validation and review findings."
    depends_on: [review-copy, review-risk]

6. Validate dependency ordering with a local script

node validate-workflow.mjs sample-repo/.archon/workflows/effloow-sandbox.yaml

Output:

{
  "workflow": "sample-repo/.archon/workflows/effloow-sandbox.yaml",
  "nodeCount": 6,
  "missingDependencies": [],
  "executionLayers": [
    [
      "inspect"
    ],
    [
      "plan"
    ],
    [
      "validate"
    ],
    [
      "review-copy",
      "review-risk"
    ],
    [
      "summarize"
    ]
  ]
}

This confirms the workflow shape expected from the docs: dependency layers can run independently, and the two review nodes form a parallel fan-out before the final summary node.

7. Docker CLI attempt

docker run --rm -v "$PWD/sample-repo:/workspace" ghcr.io/coleam00/archon:latest workflow list --cwd /workspace --json

Observed output before stopping the attempt:

Unable to find image 'ghcr.io/coleam00/archon:latest' locally

The image pull did not complete within the local run window, so Effloow Lab did not verify the Docker CLI execution path. The article must not claim that the Archon CLI successfully listed or executed the sample workflow in this sandbox.

What Worked

  • Public repo clone succeeded.
  • The current repo was inspectable without credentials.
  • Package metadata confirmed a TypeScript/Bun codebase with version 0.3.12.
  • Bundled defaults were present: 37 workflow YAML files and 36 default command files in the cloned checkout.
  • A minimal .archon/workflows/*.yaml workflow could be modeled locally.
  • Dependency validation confirmed a 6-node DAG with a two-node parallel review layer.

What Did Not Work

  • Bun was not installed on the host, so bun run cli ... was not attempted.
  • The Docker image pull did not complete within the local run window.
  • No Claude Code, Codex SDK, GitHub CLI, Slack, Telegram, or dashboard integration was executed.
  • No AI node was actually run.

Limitations

This was a structure-level sandbox, not a full Archon production trial. It validates the workflow-file concept, repository shape, bundled defaults, and DAG dependency reasoning. It does not validate model-provider behavior, credential setup, approval-node UX, web dashboard behavior, branch/worktree isolation, PR creation, or long-running workflow reliability.

Sources Checked

Read the article

This note supports the public article and records what was actually checked.

Open article →