Skip to content

maintenance: finish provider-agnostic agent setup #400

Closed

Description

@Jammy2211

Overview

Finish phase 4 of agent-agnostic setup: neutral canonical instructions, provider-aware metadata, the guarded Codex ledger branch route, and support documentation backed by a bounded real Codex smoke.

Plan

  • Move the three remaining nested canonical instruction bodies to AGENTS.md with Claude adapters.
  • Let codex/** ledger-only branches use the existing guarded merge workflow; retain code/hook/workflow exclusions.
  • Make current resume and attribution templates reflect the actual harness; preserve historical records.
  • Refresh current support prose and record a bounded installed-Codex smoke with explicit limits.
  • Validate affected code and documentation, obtain independent review, and open per-repository PRs.

Approved by the human on 2026-09-19. Branch: feature/provider-agnostic-metadata. Shared repos will stack on phase 3 (feature/codex-skill-discovery, PyAutoBrain#386); independent repo PRs target main. This is sequential work in the same session, not parallel edits to claimed repositories. Merge remains a human action.

Detailed plan and original request

Remove remaining provider assumptions from agent metadata and docs

Type: maintenance
Target: organs
Repos:

  • @PyAutoBrain
  • @PyAutoMind
  • @PyAutoMemory
  • @autofit_assistant
  • @autogalaxy_assistant
  • @autolens_assistant
  • @autocti_assistant
  • @autolens_workspace_test
    Difficulty: medium
    Autonomy: supervised
    Priority: high
    Status: draft
    Filed: 2026-09-17
    Parent: draft/maintenance/organs/agent_harness_agnostic_setup.md
    Blocked-by: codex_skill_discovery_parity

Request

Can you check that all Agent setup (skills, md files, etc) is agnostic to whether its claude or codex, been using claude for a while but gonna codex for the forseeable so worth an agnostic sweep

Scope

Move the three remaining canonical nested CLAUDE.md bodies to AGENTS.md
with thin Claude adapters; accept both claude/** and codex/** ledger branch
names; make resume metadata provider-aware; remove mandatory false
Claude/Anthropic commit attribution; and correct stale Codex hook/support
claims. Preserve historical records verbatim.

Acceptance

  • Shared canonical guidance lives in AGENTS.md; CLAUDE.md only adapts it.
  • Ledger-only session branches from either supported provider reach the same
    guarded merge path.
  • New resume and attribution metadata never guesses a provider identity.
  • Current setup/support documentation is backed by a bounded Codex smoke
    record and distinguishes tested behavior from intended support.

Resume request — 2026-09-19

Find and finish the work to make the agentic AI ecosystem agent agnostic, we should be on phase 4

Phase 3 is still PyAutoBrain#386 (approved 2026-09-17, resumed 2026-09-19).
This phase remains gated on that work; the human approved this phase in the Codex session on 2026-09-19.
Work follows phase 3, with shared-repo PRs stacked on its branch until merged.

Proposed implementation plan

Branch: feature/provider-agnostic-metadata across the listed repositories.
Classification: workspace/infrastructure. Use task worktrees inside the workspace.

  1. Move PyAutoMemory/wiki/CLAUDE.md,
    autolens_workspace_test/scripts/CLAUDE.md, and
    autolens_workspace_test/scripts/misc/database/scrape/CLAUDE.md to sibling
    AGENTS.md bodies. Replace the old files with thin imports; fix current
    links and references without rewriting historical records.
  2. Extend PyAutoMind/.github/workflows/mind_ledger_merge.yml to trigger for
    codex/** as well as claude/**. Preserve the existing default-deny path
    classifier, permissions, conflict resolver, and review boundary. Extend
    tests/test_ledger_merge.py with both branch namespaces and a workflow
    trigger assertion; verify code/hook/workflow edits remain ineligible.
  3. Replace assumed Claude resume commands in Brain start-dev/start-workspace
    registry templates and Mind REFERENCE with explicit harness/session fields.
    Record a resume command only when the active harness actually supplies it;
    unknown IDs stay unknown. Audit current consumers for assumptions before
    changing the schema. Preserve historical session records.
  4. Update the four assistant AGENTS commit-attribution rules to identify the
    actual harness/model when known, never fabricate an Anthropic identity.
    Update active setup/support prose in Brain, Mind, Memory and assistants to
    distinguish shared instructions, generated adapters, and harness-specific
    mechanisms. Verify current product claims against local installed evidence
    and official documentation where needed.
  5. Record a bounded Codex smoke: discover representative generated skills,
    resolve their canonical instructions, exercise a harmless workflow/read-only
    command, and test the applicable hook fixtures. State explicitly which
    checks exercised a real harness and which only tested adapter code. Do not
    claim full scientific-workflow or every-harness support from this smoke.
  6. Run targeted Mind ledger/hook tests, Brain discovery/template tests, adapter
    drift checks, and instruction-link checks; obtain an independent review and
    Heart verdict, then prepare one PR per affected repo. Merge is a separate
    human action. Update the parent task only against observed completion.

Branch survey — 2026-09-19

All eight phase-4 main checkouts are on main. Brain and the four assistants
are now claimed by phase 3, so phase 4 must follow it. Memory and
autolens_workspace_test are clean. Mind has an unrelated local deletion of
draft/maintenance/pyautobrain/workspace_resolver_fanout.md; preserve it.
The two assistant personal scripts noted in phase 3 also remain out of scope.

Activity

  1. Jammy2211 commented on Sep 19, 2026

    @Jammy2211
    ContributorAuthor

    provider-agnostic-metadata

    Summary

    Moved nested canonical instructions to AGENTS.md, retained thin Claude adapters, allowed codex/** ledger branches through unchanged guards, made resume and attribution metadata provider-aware, updated schema/template consumers and published a bounded Codex smoke record. Historical records preserved.

    Validation and limits

    Focused tests and independent review CLEAN. Discovery installer: 22 tests; clone profiles: 37; Mind ledger: 26; template/privacy: 111; hook adapters: 8; shared guard fixtures: 68; Brain Memory faculty: 8; Memory board: 62. Tenant firewall, scoped discovery drift, Memory structure/wikilinks, and lensing clone boundary passed. Actual Codex smoke covers discovery, not end-to-end scientific execution or every harness. Eleven pre-existing inference-assistant clone-boundary gaps remain outside this task. No template publish or release was performed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions