Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Help wanted — verify ripwire's openclaw integration on a real openclaw

Aperta Adatta ai principianti
#68 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
75/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
bash, typescript
Ambito
cli, testing-qa

Direzione di ricerca

Esegui bash scripts/verify-agent-integration.sh openclaw con un’installazione reale di openclaw e rivedi l’output di Phase 1. Incolla i due prompt in openclaw, verifica il percorso del contesto, la condizione skills-root, il comando MCP e il comportamento dell’hook, quindi incolla nuovamente nell’issue il blocco Markdown compilato; l’attività è completata quando le affermazioni sono confermate o i fallimenti sono documentati.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

help wanted

ripwire ships openclaw support as of dddd5171. Nobody maintaining this repo runs openclaw, so every
claim below is verified against docs.openclaw.ai and openclaw's own source, and none of it has been run
against a live openclaw
. This issue exists so that gap is stated in public rather than discovered by
someone installing.

If you have openclaw, this costs one command:

bash scripts/verify-agent-integration.sh openclaw

Phase 1 is automatic and installs nothing into your real home — it runs the recipe, feeds the installer
the exact flag the recipe printed, and checks the skills land and every symlink resolves, all inside a
throwaway HOME. Phase 2 prints two prompts to paste into openclaw and a filled-in markdown block to
paste back here.

A FAIL is the useful outcome. It is the only way we learn that a recipe we publish does not work.

The four claims least likely to survive contact with reality

  1. Context file. We tell users to paste the wiring into ~/.openclaw/workspace/AGENTS.md — openclaw's
    own workspace bootstrap file, NOT the repository's AGENTS.md. An earlier draft of the row said the
    repo's, which would have sent people to edit a file openclaw never reads. Is the workspace path right?
  2. Skills root and its condition. We say skills go to ~/.agents/skills — the same root Codex uses,
    which openclaw's docs call a "compatibility skill root" — and that openclaw reads it only when
    OPENCLAW_STATE_DIR is the default ~/.openclaw. We print that condition alongside the path and a
    gate fails if we ever stop printing it. Is the condition stated correctly today?
  3. MCP registration spelling. We emit
    openclaw mcp add ripwire --command <path> --arg --mcp. That is read off src/cli/mcp-cli.ts (Commander,
    --arg <value> with a required value), not run. If openclaw mcp doctor ripwire --probe disagrees,
    we are shipping a command that silently registers nothing.
  4. Hook slot. We deliberately emit no hook line for openclaw, on the grounds that its
    before_tool_call is an in-process plugin API rather than a shell-command slot like Claude Code's or
    Codex's. If openclaw does have a shell hook slot, we are under-claiming and should port ours.

What we do NOT need

Not asking anyone to advocate for ripwire, file a PR, or change anything in openclaw. Just: does the
recipe we print actually work? Paste the block, including failures.

Lingua principale
C++
Stelle
2.5k
Fork
158
Merge medio
1g 12h
PR unite (30g)
52

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di redhat-et/ripwire

Tutte le issue di redhat-et/ripwire

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.