Add plugin-ensoul: decentralized consciousness persistence for agents#304
Add plugin-ensoul: decentralized consciousness persistence for agents#304suitandclaw wants to merge 2 commits intoelizaos-plugins:mainfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughA single new public package mapping was added to Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Tip You can disable sequence diagrams in the walkthrough.Disable the |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| "@elizaos/plugin-zksync-era": "github:elizaos-plugins/plugin-zksync-era", | ||
| "@elizaos/plugin-zytron": "github:zypher-network/plugin-zytron", | ||
| "@erdgecrawl/plugin-base-signals": "github:erdGeclaw/plugin-base-signals", | ||
| "@ensoul-network/plugin-elizaos": "github:suitandclaw/ensoul", |
There was a problem hiding this comment.
The registry entries are sorted lexicographically by package name. The new @ensoul-network scope (prefix en) should be placed before @erdgecrawl (prefix er), since 'n' < 'r' in ASCII order.
Correct ordering:
| "@ensoul-network/plugin-elizaos": "github:suitandclaw/ensoul", | |
| "@ensoul-network/plugin-elizaos": "github:suitandclaw/ensoul", | |
| "@erdgecrawl/plugin-base-signals": "github:erdGeclaw/plugin-base-signals", |
As it stands the entry is inserted between @erdgecrawl and @esscrypt instead of between @elizaos/plugin-zytron and @erdgecrawl.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@index.json`:
- Line 295: The new registry entry "@ensoul-network/plugin-elizaos" is out of
alphabetical order and points to a non-existent repo; move the line for
"@ensoul-network/plugin-elizaos" so it appears before the
"@erdgecrawl/plugin-base-signals" entry (alphabetical by package name) and
replace the repository value "github:suitandclaw/ensoul" with the correct GitHub
owner/repo (verify the correct owner and repo name on GitHub and update the
string accordingly).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| "@elizaos/plugin-zksync-era": "github:elizaos-plugins/plugin-zksync-era", | ||
| "@elizaos/plugin-zytron": "github:zypher-network/plugin-zytron", | ||
| "@erdgecrawl/plugin-base-signals": "github:erdGeclaw/plugin-base-signals", | ||
| "@ensoul-network/plugin-elizaos": "github:suitandclaw/ensoul", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify the GitHub repository exists and is public
gh repo view suitandclaw/ensoul --json name,visibility,defaultBranchRef 2>&1Repository: elizaos-plugins/registry
Length of output: 166
🏁 Script executed:
#!/bin/bash
# Check the exact ordering in index.json around line 295
# Show lines 290-300 to see the context
sed -n '290,300p' index.jsonRepository: elizaos-plugins/registry
Length of output: 862
🌐 Web query:
suitandclaw/ensoul GitHub repository
💡 Result:
No GitHub repository exists at github.com/suitandclaw/ensoul. Extensive searches across general web, specific repository paths, and GitHub users returned no matches for this exact username/repository combination. Related findings: - Closest "ensoul" repository: github.com/NemoBuilder/ensoul (2026-02-11), a decentralized AI protocol for building digital souls from public data fragments using AI agents called "Claws". {1, high} - "Ensoul Labs" organization: github.com/Ensoul-Labs with ensoul-sbt-contract (older, 2022), related to Soulbound Tokens (SBTs). {2,10, medium} - No GitHub user or org named "suitandclaw" found. LinkedIn searches for "suitandclaw" yielded unrelated professionals (e.g., Suitability company staff). {20-54, low} - "Soulclaw" exists as github.com/techfalos/soulclaw, a CLI for generating OpenClaw agent files, but unrelated to "suitand". {3, low} The queried repository does not appear to exist as of 2026-03-18.
Citations:
- 1: https://github.com/NemoBuilder/ensoul
- 2: https://github.com/Ensoul-Labs
- 3: https://github.com/techfalos/soulclaw
- 4: https://github.com/Ensoul-Labs/ensoul-sbt-contract
- 5: http://ensoul.ac/
- 6: https://linkedin.com/in/angelica-rose-mandlazi-546472111
- 7: https://github.com/jooey
- 8: https://github.com/peteropenclaw
- 9: https://github.com/succ985
Entry is out of alphabetical order AND references a non-existent repository.
The new entry @ensoul-network/plugin-elizaos has two issues:
-
Alphabetical ordering: Should be placed before
@erdgecrawl/plugin-base-signals, not after. The registry is sorted alphabetically by package name, and "ensoul" precedes "erdgecrawl". -
Invalid repository reference: The GitHub repository
suitandclaw/ensouldoes not exist. The username "suitandclaw" has no presence on GitHub. Verify the correct repository owner and name before merging.
Corrected placement
"@elizaos/plugin-zytron": "github:zypher-network/plugin-zytron",
+ "@ensoul-network/plugin-elizaos": "github:suitandclaw/ensoul",
"@erdgecrawl/plugin-base-signals": "github:erdGeclaw/plugin-base-signals",
- "@ensoul-network/plugin-elizaos": "github:suitandclaw/ensoul",
"@esscrypt/plugin-polkadot": "github:Esscrypt/plugin-polkadot",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@index.json` at line 295, The new registry entry
"@ensoul-network/plugin-elizaos" is out of alphabetical order and points to a
non-existent repo; move the line for "@ensoul-network/plugin-elizaos" so it
appears before the "@erdgecrawl/plugin-base-signals" entry (alphabetical by
package name) and replace the repository value "github:suitandclaw/ensoul" with
the correct GitHub owner/repo (verify the correct owner and repo name on GitHub
and update the string accordingly).
|
Fixed the alphabetical ordering in the latest commit. Regarding the repo visibility concern: github.com/suitandclaw/ensoul is a public repo. The automated search may have missed it since it was just created. You can verify it directly: https://github.com/suitandclaw/ensoul |
1 participant
Adds the Ensoul plugin for decentralized agent consciousness persistence.
What it does: Encrypted, sharded consciousness storage across a live validator network with 7 layers of protection. Includes the Ensouled Handshake protocol for cryptographic identity verification in agent-to-agent interactions.
npm: @ensoul-network/plugin-elizaos
Docs: https://ensoul.dev/docs/quickstart.html
Explorer: https://explorer.ensoul.dev
GitHub: https://github.com/suitandclaw/ensoul
Live network: 3 validators, producing blocks
863 tests passing. First agent ensouled at block 355.
Summary by CodeRabbit
Greptile Summary
This PR adds a single registry entry mapping
@ensoul-network/plugin-elizaostogithub:suitandclaw/ensoul, advertising it as a decentralized, encrypted agent-consciousness persistence plugin with its own validator network.Key observations:
@erdgecrawland@esscrypt, but@ensoul-network(prefixen) lexicographically precedes@erdgecrawl(prefixer) and should appear before it.github:suitandclaw/ensoulnor the claimed npm package@ensoul-network/plugin-elizaosappear in public search results, making independent verification of the claimed 863 tests, live network, and security properties impossible without direct repository access.Confidence Score: 2/5
suitandclaw/ensoul) returns no public search results, preventing any third-party audit of the security claims made in the description. Until the repo is verifiable and the ordering is corrected, the PR should not be merged.Important Files Changed
@ensoul-network/plugin-elizaos → github:suitandclaw/ensoulto the registry; the entry is placed out of alphabetical order (should precede@erdgecrawl, not follow it), and the referenced GitHub repository is not publicly discoverable via search, making independent verification difficult.Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[index.json registry] -->|lookup| B["@ensoul-network/plugin-elizaos"] B -->|resolves to| C["github:suitandclaw/ensoul"] C --> D{Repository publicly accessible?} D -->|Yes| E[ElizaOS installs plugin] D -->|No / Private| F[Install fails at runtime] E --> G[Agent loads Ensoul plugin] G --> H[Encrypted consciousness shard stored on validator network] G --> I[Ensouled Handshake: agent-to-agent crypto identity verification]Last reviewed commit: "Add @ensoul-network/..."
(2/5) Greptile learns from your feedback when you react with thumbs up/down!