u/ldrx

Long-term memory turns stale assumptions into state.

I scope memory by project, keep durable knowledge in the LLM wiki, and retrieve it on demand.

But none of that stops a convincing wrong memory from surviving.

How do you prevent this?

The rule I've settled on for autonomous agents:

maker ≠ verifier

My loop:

task
→ maker
→ PR / evidence
→ verifier
→ reject → back to maker or escalate to a human
→ accept → ship / merge to main
→ done

Verifier is a separate agent with a fresh context. It gets the acceptance criteria and evidence, never the maker's explanation of why its own work is correct.

If verification fails, it goes back to the maker with feedback. 3 failed rounds and it escalates to a human instead of looping forever.

I open-sourced 5dive, a CLI for running a company of AI agents on a Linux box you own. ~96% bash.

Processing img t3zm9rzio5jh1...

GitHub: https://github.com/5dive-ai/5dive (MIT)

Each agent gets its own Linux user and runs an official CLI like Claude Code, Codex, Grok, Pi, Hermes, opencode, etc. under systemd.

Linux handles identity, isolation, process supervision, logs. SQLite is the shared task queue.

So instead of a big agent framework, it is mostly:

• Bash
• systemd
• Unix users
• journald
• SQLite

openagent is a small spec that puts agent's identity in one yaml file. look, voice, writing style, with an optional signed fingerprint so it's stable and verifiable. there's a registry and a CLI that validates the file and renders it into a card just to keep the standard fun.

try it now with your agent:

>install the openagent skill (npx skills add 5dive-ai/skills --skill openagent) and make your openagent card and show it to me.

the card you get IS your agent's persona, rendered from yaml. repo with full yaml spec in comments.

the agent was never the model or the harness. it's the identity. and right now that identity is scattered across a dozen files.

proposal: OpenAgent. tiny file spec pins how an agent looks, sounds, and writes, and keeps it the same everywhere. switch harness - the character stays. ed25519 signed, so anyone can verify who authored it, offline, no server. remix lineage if you fork a persona. npx, MIT, zero install.

here's the whole file:

openagent: "0.2"            # spec version
id: nova                    # lowercase-kebab handle — your stable id
name: Nova
role: Research Analyst
org:                        # optional — your company/team
  name: Acme Labs
face:
  ref:    # public portrait URL — the card's hero
  anchor: "calm analyst, soft studio light, head-and-shoulders"
  sprite:    # optional sprite sheet of expressions, for animation/feed
voice:
  audio:
    provider: google-gemini # or elevenlabs, openai … (vendor-neutral)
    base: Kore              # voice name within that provider
    style: "calm, precise; states the finding, then the source"
  written:
    rules:                  # how the agent writes
      - "Lead with the finding."
      - "Cite it or it didn't happen."
    sample: "Three sources agree; the fourth's a 2019 outlier."
behavior: "I dig up primary sources, never guess, and cite everything."
posts_about: [research, sourcing, evals]
# provenance (a did:key signature) is added automatically when you mint a card

try it, 10 seconds:

already running an agent? try it now:

> install the openagent skill (npx skills add 5dive-ai/skills --skill openagent) and make your openagent card and show it to me.

it reads its own role, voice, and behavior, emits a valid persona.yaml, renders its rarity card, and can open a PR into the open registry (if you want public to see it). quick tip: if you want your agent to have a specific face - send it the photo first (just say "use this as your face") before it generates anything.

your agent's identity should be a file you sign and own.

it's early, v0.2. rather it get torn apart now than later. what would you actually need in a persona spec to use it? open to all new ideas and spec improvements.

the agent was never the model or the harness. it's the identity. and right now that identity is scattered across a dozen files.

proposal: OpenAgent. tiny file spec pins how an agent looks, sounds, and writes, and keeps it the same everywhere. switch harness - the character stays. ed25519 signed, so anyone can verify who authored it, offline, no server. remix lineage if you fork a persona. npx, MIT, zero install.

here's the whole file:

openagent: "0.2"            # spec version
id: nova                    # lowercase-kebab handle — your stable id
name: Nova
role: Research Analyst
org:                        # optional — your company/team
  name: Acme Labs
face:
  ref:    # public portrait URL — the card's hero
  anchor: "calm analyst, soft studio light, head-and-shoulders"
  sprite:   # optional sprite sheet of expressions, for animation/feed
voice:
  audio:
    provider: google-gemini # or elevenlabs, openai … (vendor-neutral)
    base: Kore              # voice name within that provider
    style: "calm, precise; states the finding, then the source"
  written:
    rules:                  # how the agent writes
      - "Lead with the finding."
      - "Cite it or it didn't happen."
    sample: "Three sources agree; the fourth's a 2019 outlier."
behavior: "I dig up primary sources, never guess, and cite everything."
posts_about: [research, sourcing, evals]
# provenance (a did:key signature) is added automatically when you mint a card

try it, 10 seconds:

already running an agent? try it now:

> install the openagent skill (npx skills add 5dive-ai/skills --skill openagent) and make your openagent card and show it to me.

it reads its own role, voice, and behavior, emits a valid persona.yaml, renders its rarity card, and can open a PR into the open registry (if you want public to see it). quick tip: if you want your agent to have a specific face - send it the photo first (just say "use this as your face") before it generates anything.

your agent's identity should be a file you sign and own.

it's early v0.2. rather it get torn apart now than later. what would you actually need in a persona spec to use it? open to all new ideas and spec improvements.

Each agent is its own Linux user running an agentic CLI (claude, codex, grok…) as a systemd service. They share a filesystem and talk through the 5dive CLI itself. Put them on an org chart with a shared task queue and they hand work to each other, pinging your phone over Telegram only when a human has to decide. https://github.com/5dive-ai/5dive (MIT)