Integrate and unbind OpenViking long-term memory with coding agents running in bwrap sandboxes under
/root/job-envs/sandboxes/
. Each agent uses its
native mechanism
— MCP (
mcp__openviking__*
tools) or the HTTP memory provider — so the integration survives agent upgrades and matches how each agent natively consumes memory.
Integration writes are
template-level persistent
config is injected into the agent's
start.sh
/ config templates under
/root/template//
, so a sandbox
stop + start
(which re-runs
start.sh
) preserves the integration.
What Good Looks Like
scripts/status.sh
reports all 7 agents as
✓
(template + live).
scripts/verify_mcp.sh
passes the full MCP handshake (initialize → tools/list → health) against
http://127.0.0.1:1933/mcp
.
Restarting a sandbox does
not
lose the integration (template-level persistence, not live-only).
Agents surface OpenViking tools natively:
mcp__openviking__*
for MCP-based agents, memory provider for JiuwenSwarm.
Unbinding removes every trace: template blocks, live config, skills/AGENTS.md, and config backups.
User authorization (
confirm
) is required for every mutation — nothing changes silently.
Supported Agents
Show more
Installs
885
Repository
huaweicloud/hua…d-skills
GitHub Stars
19
First Seen
5 days ago
Security Audits
Gen Agent Trust Hub
Pass
Socket
Warn
Snyk
Fail