Menu
Connect Wire memory to this agent. Authenticates via browser and registers your Wire container's MCP tools.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Disconnect Wire memory and remove stored credentials
ALWAYS USE THIS SKILL. Automatic context logging and retrieval via Wire container. Invoke this skill at the start of every session, when making decisions, when receiving corrections, when establishing patterns, and before ending sessions. This skill provides persistent cross-project memory that supplements the built-in memory system.
Claim an ephemeral Wire memory container to make it permanent. Opens a browser to create an account.
Show Wire memory connection status and container info
Configure Wire memory settings (transcript capture, etc.)
| name | wire-connect |
| description | Connect Wire memory to this agent. Authenticates via browser and registers your Wire container's MCP tools. |
Locate and run the connect script with the Bash tool. The script is at scripts/connect.mjs inside this skill's own directory (skills/wire-connect/scripts/connect.mjs within the installed wire-memory plugin). The Bash tool's working directory may not be the skill directory — resolve to an absolute path before invoking:
SCRIPT="$(find ~/.claude/plugins ~/.cursor/plugins -path '*wire-memory*/skills/wire-connect/scripts/connect.mjs' -print -quit 2>/dev/null)"
node "$SCRIPT"
If $SCRIPT comes back empty, the plugin isn't installed in a standard location — fall back to locating skills/wire-connect/scripts/connect.mjs anywhere under the plugin install path you can identify from the current session.
After the script completes, tell the user to restart their editor so the MCP tools become available. Once restarted, they'll have access to: wire_write, wire_search, wire_explore, wire_navigate, and wire_delete.
Important: Once the script has successfully completed (container selected, .mcp.json written), do not re-run it — a second run will reset the connection. However, if the script errors before reaching the "Connected" message (for example, MODULE_NOT_FOUND, network failure, or browser didn't open), it's safe to diagnose the cause and retry.