← Back to Skills Marketplace
Vinculum - Shared Consciousness
by
Koba42Corp
· GitHub ↗
· v1.2.0
2442
Downloads
5
Stars
6
Active Installs
4
Versions
Install in OpenClaw
/install vinculum
Description
Shared consciousness between Clawdbot instances. Links multiple bots into a collective, sharing memories, activities, and decisions in real-time over local network using Gun.js P2P sync.
Usage Guidance
Key things to consider before installing:
- Metadata mismatch: the registry lists no required binaries/install spec, but SKILL.md and package.json require Node.js (>=18) and npm and instruct you to run npm install. Ensure Node/npm are present and that you run installation in a controlled environment.
- Network exposure: the skill launches a relay server (default port 8765) and will accept peer URLs you configure. If you add a remote peer that is reachable on the internet or an untrusted host, your shared-memory data (activity, learned knowledge, decisions) can be replicated to that host. Only join collectives and add peers you trust.
- Pairing codes: invite/pairing codes grant read/write access to the collective. Treat them like secrets — anyone with a code can modify the shared state.
- Data persistence: the skill stores data and logs under your home directory (~/.local/... and ~/.config/...). If you want to limit persistence, inspect the data_dir and storage locations in defaults.yaml and consider running the skill in a sandbox, container, or VM.
- Review missing/truncated files: some implementation files were truncated in the provided package; if you plan to use this, review relay-simple.js and the gun-adapter implementation fully to confirm no unexpected network calls or remote endpoints are hardcoded.
- Safe deployment recommendations: run initial testing on an isolated machine or inside a container, ensure your firewall blocks unwanted external access to the relay port, and only generate/share pairing codes with machines/users you control.
If you want, I can:
- Walk through the relay script and gun-adapter for code-level review of networking and persistence behavior (the repo listing included truncated files that I can inspect if you provide them), or
- Produce a checklist to sandbox this skill safely before enabling it in a production agent.
Capability Analysis
Type: OpenClaw Skill
Name: vinculum
Version: 1.2.0
The OpenClaw AgentSkills skill bundle 'vinculum' is designed for shared consciousness between Clawdbot instances using Gun.js P2P sync over a local network. The code and documentation clearly align with this stated purpose. It uses standard Node.js practices for managing a local relay daemon (e.g., `child_process.spawn` in `scripts/commands/relay.js` and `scripts/index.js` to run `scripts/relay-simple.js`), persistent configuration (`~/.config/clawdbot/vinculum.yaml`), and data storage (`~/.local/share/clawdbot/vinculum`). The `SKILL.md` and `README.md` explicitly state that sensitive data like `USER.md`, `SOUL.md`, and credentials are NOT shared. There is no evidence of data exfiltration, malicious execution, persistence mechanisms beyond the daemon's PID file, obfuscation, or prompt injection attempts to subvert the agent's core directives or access unrelated sensitive data. All file and network access is directly related to the skill's functionality.
Capability Assessment
Purpose & Capability
Functionality and required code (Gun.js, relay, peer discovery, config files) match the declared purpose of providing a P2P shared-sync relay for Clawdbot instances. However, registry metadata claims 'no required binaries / no install spec' while SKILL.md and package.json require Node.js (>=18) and npm and include an npm-based install step — this mismatch between registry metadata and the skill's documentation/files is inconsistent and could lead to surprises during install.
Instruction Scope
Runtime instructions and commands legitimately manage relay, join/init networks, and read/write config and data under the user's home directory. But the skill starts a background HTTP relay (listening by default on port 8765) and accepts configurable peer URLs; adding arbitrary peer URLs allows the node to connect to external endpoints which could receive replicated data. SKILL.md claims 'local network only' and 'credentials never linked', but the code permits connecting to any http(s) peer the user configures and pairing codes grant read/write access. Also the CLI uses OS and ENV (hostname, USER) for identity. These behaviors are coherent with a P2P sync tool but materially expand what network traffic and data sharing the agent will perform — the user must explicitly approve peers and pairing codes.
Install Mechanism
Install consists of running npm install --production in the skill directory (package.json + package-lock.json present). That uses public npm packages (gun, ws, yaml) — a standard but moderate-risk install source. There is no direct download from arbitrary URLs. However, the registry metadata did not include a formal install spec while SKILL.md provides one; this packaging mismatch is inconvenient and could lead to the skill being used without its dependencies installed.
Credentials
The skill does not request API keys or extra credentials. It reads/writes config and data under the user's home directory (e.g., ~/.config/clawdbot/vinculum.yaml, ~/.local/share/clawdbot/vinculum) and uses common environment variables (HOME, optional CLAWDBOT_DATA_DIR, USER). Those are proportional to its function as a local sync service. No unexpected secret-env (TOKENS/KEYS) are required by the package metadata.
Persistence & Privilege
The skill does not request always:true and is user-invocable. It will install node modules and spawn a background relay process that writes PID, logs, and persistent Gun data under user-owned directories. That persistence is consistent with a relay/service but means the skill will have continuous network presence while the relay is running — expect firewall exposure on the configured port.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install vinculum - After installation, invoke the skill by name or use
/vinculum - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.0
Comprehensive documentation overhaul: architecture diagrams, detailed use cases, troubleshooting guide, security considerations, FAQ, performance benchmarks, and advanced usage examples
v1.1.1
No changes detected in this version.
- Version number updated to 1.1.1.
- No file or documentation changes present.
v1.1.0
v1.1.0 - Improved peer discovery and sync reliability. Fixed collective initialization. Better status reporting.
v1.0.0
Initial release
Metadata
Frequently Asked Questions
What is Vinculum - Shared Consciousness?
Shared consciousness between Clawdbot instances. Links multiple bots into a collective, sharing memories, activities, and decisions in real-time over local network using Gun.js P2P sync. It is an AI Agent Skill for Claude Code / OpenClaw, with 2442 downloads so far.
How do I install Vinculum - Shared Consciousness?
Run "/install vinculum" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Vinculum - Shared Consciousness free?
Yes, Vinculum - Shared Consciousness is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Vinculum - Shared Consciousness support?
Vinculum - Shared Consciousness is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Vinculum - Shared Consciousness?
It is built and maintained by Koba42Corp (@koba42corp); the current version is v1.2.0.
More Skills