convez.ai
AgenteAutomaçãoIntermediário
strata-space

Strata Memory

strata-space/strata-memory-plugin

Memória persistente com busca inteligente para agentes de código

Ver no GitHub
InicialPluginScore · de 0 a 100

Plugin que transforma um Strata Space em memória de longo prazo para agentes de código (Claude Code e Codex). Implementa busca híbrida (palavra-chave + semântica) para recuperar documentos relevantes a cada prompt, contrato de atualização automática e verificação de consistência entre mudanças de código e documentação.

Instalação

$npx convez-ai strata-space/strata-memory-plugin

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
71%
Último commit
há 1 mês
Versão
strata-memory--v1.0.0
Issues abertas
1
Contribuidores
1

Casos de uso

  • Manter agentes de IA atualizados com convenções e padrões do projeto
  • Recuperar automaticamente documentação relevante a cada sessão de coding
  • Sincronizar mudanças de código com atualizações de documentação

Veredito

Solução bem pensada para um problema real: agentes de IA esquecendo contexto entre sessões. A abordagem fail-open e os hooks de lifecycle mostram implementação madura; ideal para equipes que usam agentes em codebases com documentação viva.

README

A tradução para o português deste README ainda está na fila.

Strata Memory

Your coding agent forgets everything between sessions. Point it at a Strata Space and it stops forgetting.

strata-memory is a plugin for Claude Code and Codex that turns a Strata Space (your design notes, conventions, gotchas, runbooks) into the agent's long-term memory:

  1. Recall, on every prompt. The plugin hybrid-searches (keyword + semantic) the bound Space on your prompt and injects the matching documents as candidates: title, document ID, snippet, score. The agent reads the ones that are genuinely relevant and ignores the rest.
  2. A standing contract. Alongside the candidates, once per session: if you rely on one of these documents and your work changes a fact in it, update that document before you finish. The agent writes back through the normal Strata edit surface (MCP edit_document, or strata api documents edit).
  3. A gentle nudge. When the agent stops after changing files without updating any memory document it relied on, the plugin blocks the stop once and asks it to reconcile. Strictness is configurable; uncertain signals always resolve to "allow".

Recall is fail-open by design: a slow or unreachable backend can never block or delay your prompt. The hooks run the strata CLI under tight internal time budgets and silently no-op on any failure.

Requirements

  • A Strata account and a Space with the documents you want remembered

  • The strata CLI, version 3.3.0 or newer:

    brew install --cask strata-space/tap/strata
    

Install

Claude Code

/plugin marketplace add strata-space/marketplace
/plugin install strata-memory@strata-space

Codex

Add the marketplace source and enable the plugin (or install it from the Codex app's plugin directory):

# ~/.codex/config.toml
[plugins."strata-memory@strata-space"]
marketplace = "github:strata-space/marketplace"

Then run /plugins in Codex and install strata-memory.

Quickstart

strata login
cd your-repo
strata memory init        # pick a Space interactively, or:
strata memory bind space_01ABC...            # just you
strata memory bind space_01ABC... --scope project   # whole team (commits .strata/memory.json)

Start a session in that repository. Relevant memory documents appear in a <strata-memory> block as you prompt; strata memory status shows the resolved binding at any time. The bundled skills walk through setup (strata-memory-init) and diagnosis (strata-memory-status) in conversation.

How it works

The plugin wires four lifecycle hooks into thin wrappers around strata memory <verb>:

HookVerbWhat it does
SessionStartpreflightVerifies auth + binding, seeds the session ledger with a git baseline, warns when semantic search is degraded, injects a compact Space index
UserPromptSubmitrecallSearches the Space on your prompt; injects deduplicated candidates plus the once-per-session update contract; records each candidate's document version
PostToolUseobserveMarks candidates the agent actually read (MCP read_document, or strata api documents get)
StopcheckNudges (at most once per session by default) when files changed but no relied-upon document's version moved

Write-back detection is transport-agnostic: any edit path that goes through Strata bumps the document version, so the stop check works whether the agent edited via MCP or the CLI.

State lives with the CLI, not the plugin: bindings in the platform data dir (shared across hosts), one ledger per session, garbage-collected after seven days. A committed .strata/memory.json (project scope) wins over a personal binding.

Configuration

Per-binding config (set at bind time, or edit the binding file):

KeyDefaultMeaning
strictnessnudgeOnceoff (never block), nudgeOnce (block at most once per session), strict (keep nudging, capped)
topK5Max candidate documents injected per prompt
minScore0Drop candidates below this RRF score
recallTimeoutMs2000Hard wall-clock budget for recall
injectIndextrueInject a compact Space index at session start

Environment overrides (STRATA_MEMORY_STRICTNESS, STRATA_MEMORY_TOP_K, STRATA_MEMORY_MIN_SCORE, STRATA_MEMORY_RECALL_TIMEOUT_MS, STRATA_MEMORY_INJECT_INDEX) beat the binding file.

Privacy

Recall sends your prompt text to Strata's search API for the bound Space. Results are scoped to what your Strata user may read; the agent can only retrieve and edit documents you have access to. The update contract instructs agents to never write secrets or raw transcripts into memory.

Troubleshooting

Ask your agent to run the strata-memory-status skill, or check by hand:

strata memory status --json   # binding, scope, config, ledger count
strata status --json          # auth state

Recall not injecting anything? Short or acknowledgement prompts are skipped by design, and documents already surfaced in the session are not repeated. No binding resolves? The binding key is the git repo root; bind from inside the repository.

Installing this alongside the strata plugin is supported: both bundle the same MCP server registration, which the hosts namespace per plugin (you will see the Strata tools twice).

Development

shellcheck -x scripts/*.sh tests/*.sh
bash tests/hooks-json-valid.sh
bash tests/wrapper-fail-open.sh
bash tests/wrapper-passthrough.sh
bash tests/wrapper-protocol-shape.sh
bash tests/live-cli-smoke.sh   # skips without the strata CLI

Releases are cut by release-please from Conventional Commits; both host manifests version-bump in lockstep.

License

MIT

Ver o original no GitHub

Bom para

Relacionados