Skip to content

Instantly share code, notes, and snippets.

@goern
Created March 16, 2026 17:53
Show Gist options
  • Select an option

  • Save goern/5f361386ded9a5f0c848112ea8fe6f4d to your computer and use it in GitHub Desktop.

Select an option

Save goern/5f361386ded9a5f0c848112ea8fe6f4d to your computer and use it in GitHub Desktop.
Main (Apex) agent session analysis — 8 problems identified with dependency graph (2026-03-16)

Main Agent (Apex) Session Analysis

Session: 7c1c3d95-e938-4dac-9602-b2a06fed4870 Period: 2026-03-14 03:20 UTC → 2026-03-16 ~09:19 UTC Entries: 108 JSONL lines


Identified Problems

P1: beads.role not configured

Severity: Low (cosmetic warning) Frequency: Every bd create call (entries 30, 46, 54-64, 68, 80, 86, 94, 102, 106) Error:

warning: beads.role not configured. Run 'bd init' to set.

Impact: No functional impact, but pollutes output and may confuse agents parsing tool results. Fix: Run bd init in the main agent's workspace, or set beads.role in config.


P2: dolt_server_port deprecation warning

Severity: Low (cosmetic warning) Frequency: Every bd show/bd list call (entries 36, 40, 44, 48) Error:

Warning: dolt_server_port in metadata.json is deprecated (can cause cross-project data leakage).
  The port file (.beads/dolt-server.port) is now the primary source.
  Remove dolt_server_port from .beads/metadata.json to silence this warning.

Impact: Noise in tool results. Potential cross-project data leakage if not migrated. Fix: Remove dolt_server_port from .beads/metadata.json.


P3: AGENTS.md path incorrect in workspace

Severity: Medium Occurrence: Entry 22 Error:

{"status": "error", "tool": "read", "error": "Sandbox FS error (ENOENT): /home/openclaw/.openclaw/workspace/AGENTS.md"}

Impact: Main agent cannot read the agent roster from its expected location. Had to fall back to reciting from memory (system prompt injection), which may be stale. Fix: Ensure AGENTS.md exists at /home/openclaw/.openclaw/workspace/AGENTS.md or update the workspace bootstrap to symlink/copy it.


P4: Indago sandbox missing research repo mount

Severity: Critical Occurrence: Discovered via bead intercom-5y4 comments Error:

/bin/sh: line 1: cd: /workspace/repos/research: No such file or directory
mkdir: cannot create directory '/workspace/repos': Permission denied

Impact: Indago cannot commit research output. Entire research→PR pipeline is broken. Tracked: GitHub Issue #56


P5: GITHUB_TOKEN scope too narrow

Severity: Critical Occurrence: Entries 42-49, bead intercom-7c3.2.2 Error:

remote: Write access to repository not granted.
fatal: unable to access 'https://github.com/b4arena/ludus.git/': The requested URL returned error: 403

Impact: Forge blocked on all repos except tabula. Cannot commit code to ludus or test-greeter. Tracked: GitHub Issue #59


P6: Main agent reports stale bead state

Severity: Medium Occurrence: Entries 93-99 Symptom: Main reported intercom-zjp was still in progress when it had already been closed by helm. User had to correct main twice. Root cause: Main did not re-fetch bead status before reporting. It relied on cached/in-memory state from when it created the bead. Fix: Add a "refresh before report" rule to main's SOUL.md — always bd show a bead before reporting its status to the user.


P7: Helm failed to assign GitHub issue #56 to durandom

Severity: High Occurrence: Entries 100-103 Symptom: Helm reported it created issue #56 and assigned it to durandom. User verified it was NOT assigned. Main had to create a follow-up investigation bead (intercom-8n3). Root cause: Likely the gh issue create --assignee durandom command failed silently (no org permission to assign), or helm hallucinated the assignment. Impact: Breaks the escalation→human handoff pipeline. If agents report actions they didn't complete, trust erodes. Fix: (a) Verify helm's gh CLI permissions include assignee rights, (b) Add post-action verification to agent SOULs — after creating an issue, gh issue view to confirm state.


P8: Tabula research URLs return empty responses

Severity: Medium Occurrence: Discovered in indago session (bead intercom-5y4) URLs:

https://tabula.b4madservice.workers.dev/research/verification-loop-gap  → 0 bytes
https://tabula.b4madservice.workers.dev/research/outcomes-outputs-results → 0 bytes

Impact: Indago had to work with only the GitHub-hosted SOUL.md as source material. Research quality degraded. Fix: Deploy content to these Tabula endpoints or remove them from research task templates.


Dependency Graph

                    ┌─────────────────────────────┐
                    │  P5: GITHUB_TOKEN scope      │
                    │  (Critical — Issue #59)       │
                    └──────────┬──────────────────┘
                               │ blocks
                               ▼
                    ┌─────────────────────────────┐
                    │  forge can't push to ludus   │
                    │  or test-greeter             │
                    └──────────┬──────────────────┘
                               │ blocks
                               ▼
              ┌────────────────────────────────────┐
              │  intercom-qy9: commit indago's     │
              │  research to ludus repo             │
              └────────────────────────────────────┘
                               ▲ caused by
                               │
                    ┌──────────┴──────────────────┐
                    │  P4: indago sandbox missing   │
                    │  /workspace/repos/research    │
                    │  (Critical — Issue #56)        │
                    └──────────┬──────────────────┘
                               │ triggered
                               ▼
                    ┌─────────────────────────────┐
                    │  P7: helm failed to assign    │
                    │  GH#56 to durandom            │
                    │  (High — trust issue)          │
                    └──────────┬──────────────────┘
                               │ caused
                               ▼
                    ┌─────────────────────────────┐
                    │  P6: main reports stale state │
                    │  (Medium — process gap)        │
                    └─────────────────────────────┘


        Independent Issues (no upstream dependencies):

        ┌──────────────────┐  ┌──────────────────┐  ┌──────────────────┐
        │ P1: beads.role   │  │ P2: dolt_server  │  │ P3: AGENTS.md    │
        │ not configured   │  │ _port deprecated │  │ path missing     │
        │ (Low)            │  │ (Low)            │  │ (Medium)         │
        └──────────────────┘  └──────────────────┘  └──────────────────┘

        ┌──────────────────┐
        │ P8: Tabula URLs  │
        │ return empty     │
        │ (Medium)         │
        └──────────────────┘

Causal Chain (main storyline)

P4 (indago can't write)
  → indago posts research as bead comment (workaround)
  → main delegates commit to forge (intercom-qy9)
  → P5 (forge can't push to ludus) blocks commit
  → main delegates fix to helm (intercom-zjp)
  → helm can't fix from sandbox → creates GH#56
  → P7 (helm didn't actually assign to durandom)
  → user catches discrepancy
  → P6 (main reports stale state, doesn't verify)
  → user has to correct main twice
  → trust erosion in agent reporting

Priority Order for Fixes

Priority Problem Fix Effort Impact
1 P5 — GITHUB_TOKEN scope 5 min (PAT settings) Unblocks all forge work
2 P4 — indago research mount 15 min (container config) Unblocks indago pipeline
3 P7 — agent action verification 30 min (SOUL.md update) Prevents false reports
4 P6 — stale state reporting 15 min (SOUL.md update) Prevents user frustration
5 P3 — AGENTS.md workspace path 5 min (bootstrap fix) Correct agent roster
6 P8 — Tabula research endpoints varies (content deploy) Better research quality
7 P1 — beads.role warning 2 min (bd init) Clean output
8 P2 — dolt_server_port 2 min (edit metadata.json) Clean output + safety
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment