cloud1
cloud2
cloud3
cloud4
cloud5
cloud6
Sync plugin
Syndu Sync Plugin
← Back to platform brief
Sync plugin

Syndu Sync Plugin

Syndu Sync gives Codex governed memory instead of disposable chat state. Install the local plugin, connect the right workspace in the browser, then use self memory, shared spaces, nested workspaces, snapshots, and semantic method capture across future runs.

Download plugin Open Memory Workspaces Open Sync guide
Install by prompt

Copy this prompt into Codex in the workspace where you want Syndu Sync installed

This is a user prompt for Codex. It installs the Sync plugin, warns before the browser handoff, opens Memory Workspaces, and lets the user provision the first Sync key only if the shell needs direct bearer fallback.

Codex, visit https://syndu.com/pages/resources/sync-plugin/, install the Syndu Sync plugin in this workspace, tell me before the browser handoff opens, run codex mcp login syndu if needed, and after approval land me on Memory Workspaces so I can provision the Sync key for this shell if I want bearer fallback.
This is a prompt for Codex Download into this workspace Expect a browser handoff Land on Memory Workspaces after approval Create a Sync key only when needed
Documentation index Platform brief Quota rules Privacy FAQ
Current bundle
v0.2.0 · 67 KB

A local Sync bundle from Syndu Web LTD with the plugin manifest, hosted Sync connection surface, install docs, and marketplace metadata.

Download zip
Hosted endpoint
https://syndu.com/sync-mcp/

The plugin points at Syndu's hosted Sync MCP surface for governed memory, nested workspaces, semantic method capture, and workspace snapshots.

Install path
./plugins/syndu

Put the unpacked plugin inside the workspace. Codex accepts relative local plugin paths for marketplace installs.

First destination
Memory Workspaces

After the first browser approval, the correct control plane is Memory Workspaces, where the user can provision the first Sync key and manage governed spaces.

Open Memory Workspaces
Memory model
Self space, team spaces, and nested org trees

Every user starts with a self memory workspace, then expands into additional workspaces, collaborators, restricted spaces, and nested enterprise branches.

What compounds
Methods, recommendations, and durable context

Syndu Sync preserves not only what happened, but how it was done and what a future operator or agent should do next.

What The Sync Download Includes

The Sync bundle should feel operational on first install: plugin manifest, hosted Sync endpoint, install docs, and the local marketplace shape needed to put Codex into governed memory quickly.

Bundle contents

Plugin shell plus hosted Sync config

The zip includes the Codex plugin manifest, the hosted Syndu Sync endpoint definition, bundled memory skills, validation scripts, and install docs.

.codex-plugin/plugin.json .mcp.json Bundled Sync skills Validator and smoke test
Marketplace template

Fastest tested local install

The plugin should live inside the workspace and the marketplace path should stay relative.

{
  "name": "syndu-local",
  "interface": {"displayName": "Syndu Local"},
  "plugins": [
    {
      "name": "syndu",
      "source": {
        "source": "local",
        "path": "./plugins/syndu"
      },
      "policy": {"installation": "AVAILABLE", "authentication": "ON_USE"},
      "category": "Research"
    }
  ]
}
Keep the path relative Install from the Plugins tab Reuse the same workspace later
Control plane

Memory Workspaces is where setup continues

The install flow should end in Memory Workspaces, where the user can create the first Sync key, create additional workspaces, and manage collaborators and restricted spaces.

Open Memory Workspaces Create the first Sync key if needed Expand into shared workspaces later

Why Start With Syndu Sync

Syndu Sync is the governed memory product. It starts with the individual's self space, expands into shared workspaces and nested branches, and gives Codex a durable place to preserve methods and context without forcing the user into the cyber-specific toolchain.

Sync plugin

Every user starts with a self memory workspace

The default Sync shape is simple: one governed self space, one journal viewer, and one control plane that can grow as the user's work grows.

Sync plugin

Workspaces can branch without losing structure

Users can add workspaces for clients, teams, departments, or subsidiaries and keep the same memory structure at every level of the tree.

Sync plugin

Permissions stay governed and explicit

Sync supports invites, role changes, read-only versus read-write access, restricted spaces, and activity history so the memory system stays trustworthy as more people join.

Sync plugin

Methods matter as much as outcomes

The Sync memory model captures method steps, recommendations, semantic tags, and structured notes so future runs inherit the route, not just the final answer.

Sync plugin

Snapshots turn workspace memory into infrastructure

When a team needs a backup, handoff, or compliance checkpoint, Sync can capture the workspace tree and memory structure as a durable snapshot.

Open The Right Surface

A cold visitor should be able to move from the download into the right Sync control plane without hunting through the site.

Current zip

Download plugin

syndu-v0.2.0-codex-plugin.zip

Download the current installable Sync plugin bundle directly from Syndu.

Stable bundle name Local plugin install Current published version
Open document
Memory Workspaces

Provision Sync access

/workspace/memory/workspaces/

Create the Sync key for this shell, create additional workspaces, and manage the memory tree from Memory Workspaces.

Create Sync credential Open self workspace Manage governed memory
Open document
Workspace control plane

Open the Sync surface

/workspace/memory/workspaces/

Work directly with governed workspaces, invites, permissions, spaces, semantic memory, and snapshots.

Nested workspaces Spaces and grants Snapshots and exports
Open document
Specialized plugin

Explore CyberSync

/pages/resources/cybersync-plugin/

Move into the cyber-security enterprise layer when the governed memory loop needs outside-in cyber context and shared global signal.

Cyber plugin Enterprise fit Hosted cyber MCP
Open document

What Sync Is For

Sync is the core memory product. It should stay distinct from the cyber-specialized plugin even though both live in the same ecosystem.

Individual

Self memory and private continuity

Best when one operator wants durable context, semantic notes, methods, and snapshots without involving a larger team yet.

Self workspace Journal viewer Snapshot-ready continuity
Team

Shared workspaces and governed access

Best when a team needs invites, roles, read-only versus read-write boundaries, and clear activity history around the same memory tree.

Invites and revoke flow Restricted spaces Nested workspace branches
Specialized enterprise

Step into CyberSync when the memory needs cyber context

Best when the workflow needs outside-in cyber investigation, hosted MCP tools, and global information sharing on top of the governed memory system.

Cyber investigation Global signal sharing CyberSync MCP alignment

Download, Install, Connect

The Sync install path should feel calm: install the bundle, approve the browser handoff, land on Memory Workspaces, and start using governed memory instead of wrestling with setup.

01

Download the current bundle

Grab the latest Syndu Sync zip from this page so the buyer starts from a packaged local plugin.

02

Unzip it into this workspace

Expand the bundle inside the repo or workspace where Codex will run, so the plugin lands at `./plugins/syndu`.

03

Point Codex at the relative plugin path

Use the bundled marketplace template as `.agents/plugins/marketplace.json` and keep the source path relative, for example `./plugins/syndu`.

04

Install Syndu Sync in the Plugins tab

Open the Plugins tab, switch to the Syndu Local marketplace, and install Syndu Sync just like any other local plugin bundle.

05

Let Codex trigger the browser approval step

The first live request, or an explicit `codex mcp login syndu`, opens Syndu's browser approval flow so the user can sign in and connect the workspace cleanly.

06

Land in Memory Workspaces

After approval, Syndu opens Memory Workspaces so the operator can create the first Sync key for the shell if direct bearer fallback is wanted.

07

Start with self memory, then expand

Use the default self workspace first, then create additional workspaces, collaborators, restricted spaces, and snapshots only when the workflow needs them.

Copy-Ready Install Snippets

Give operators the fewest moving parts possible: download, unpack, add marketplace metadata, let Codex narrate the browser handoff, then finish in Memory Workspaces.

bash

Download and unpack locally

mkdir -p ./plugins ./.agents/plugins
curl -L -o syndu-v0.2.0-codex-plugin.zip "https://syndu.com/pages/resources/sync-plugin/download/"
unzip -o syndu-v0.2.0-codex-plugin.zip -d ./plugins
json

Repo marketplace entry

{
  "name": "syndu-local",
  "interface": {"displayName": "Syndu Local"},
  "plugins": [
    {
      "name": "syndu",
      "source": {
        "source": "local",
        "path": "./plugins/syndu"
      },
      "policy": {"installation": "AVAILABLE", "authentication": "ON_USE"},
      "category": "Research"
    }
  ]
}
text

Connect, then land on Memory Workspaces

Codex, run codex mcp login syndu if needed, wait for me to finish browser approval, then tell me when Memory Workspaces is open so I can decide whether to create the first Sync key for this shell.

Related Resources

Documentation

Syndu Documentation Index

Syndu gives computer-using agents governed memory, shared workspace context, and specialized cyber intelligence when the workflow needs it. This index maps the two plugin tracks, the hosted cyber MCP workflows, the Risk API, pricing, privacy, and the evidence depth behind the system.

4 briefing points Documentation
Open article
Coverage

What Syndu Reports Cover

Syndu exposes a dimensional risk surface across network entities and geography: ip address, subnet, ISP, ASN, organization, city, region, and country. That same dimensional graph powers the Risk API, MCP tools, and the memory loop that preserves the resulting decisions.

4 briefing points Coverage
Open article
Operations

Using Syndu with SoC and SIEM Workflows

Syndu is an external context layer for monitoring, hygiene review, agent workflows, and decision support. It complements SoC and SIEM processes rather than replacing them, while sharing the same evidence and memory model used elsewhere on the platform.

4 briefing points Operations
Open article
Fraud operations

Using Syndu with Fraud, Payments, and Merchant-Risk Workflows

Syndu is also a decision surface for fraud, payments, merchant-risk, and trust workflows. The same outside-in evidence graph, Risk API, and governed memory loop help teams score, review, and preserve conclusions around risky identifiers.

4 briefing points Fraud operations
Open article
AI and scale

Consuming Syndu at Scale

The platform supports three access surfaces at scale: direct report access for large-scale browser or agent consumption, the Risk API for application-native scoring, and the MCP server for collaborative agent workflows.

4 briefing points AI and scale
Open article
Delivery modes

Direct, API, and MCP Access

Syndu is one platform with three access surfaces: direct access for report-shell consumption, API access for application-side scoring, and MCP access for agent collaboration. They sit under the same workspace, quota, and subscription control plane, but differ in delivery contract.

4 briefing points Delivery modes
Open article
Register

Create a workspace to govern access to Syndu.

Registration unlocks the workspace control plane, plan selection, credential provisioning, and the subscription flow across web, API, and MCP access.

Register Sign in to workspace