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

Syndu Codex Plugin

Syndu Web LTD gives Codex shared risk memory, outside-in risk context, and a governed place to preserve approved conclusions across future runs. Install the local plugin, connect the workspace in the browser, finish shell setup in the Syndu workspace Access Dashboard, then validate the loop with `sync`, `commit`, and the Memory Journal graph.

Download plugin Open Access Dashboard Open MCP page Open Memory Journal
Install by prompt

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

This is a user prompt for Codex. It tells Codex to install the plugin, warn before the browser handoff, guide the user into the Syndu workspace Access Dashboard, and then validate the external memory loop with `sync` and `commit`.

Codex, visit https://syndu.com/pages/resources/codex-plugin/, install or reinstall the Syndu plugin in this workspace, tell me before the browser handoff opens, run codex mcp login syndu when needed, then guide me through the Syndu workspace Access Dashboard so I can create the MCP key for this shell. After that, run sync against my default Syndu memory space, create a commit titled "Codex reinstall checkpoint", and send me to the Memory Journal so I can inspect the graph. If I am backfilling, pass occurred_at so the commit is inserted into the correct previous/next timeline slot.
This is a prompt for Codex Download into this workspace Expect a browser handoff Finish by pasting the Access Dashboard prompt into the same shell Validate with sync and commit
Documentation index Platform brief Quota rules Privacy FAQ
Current bundle
v0.1.13 · 70 KB

A polished local bundle from Syndu Web LTD with the plugin manifest, hosted connection surface, sigil-led branding, install docs, and a ready-to-edit marketplace template.

Download zip
Connection model
Approve in browser, finish in the Access Dashboard

Codex installs the plugin first, then Syndu opens browser approval and the MCP section of the Access Dashboard so the operator can provision owned workspace access and investigation quota for the same workspace.

Install path
./plugins/syndu

Put the unpacked plugin inside the workspace. Codex accepts relative local plugin paths and rejects absolute ones for marketplace installs.

Hosted endpoint
https://syndu.com/mcp/

The plugin points at Syndu's hosted MCP endpoint, so the buyer installs a bundle instead of running a bridge.

Fresh signal
10-minute community demand

Codex investigations now return whether public analyst demand is clustering around the same entity, including recent query windows and requester convergence.

Shell credential
Create the MCP key in the Access Dashboard

The browser approval gets the user into the right workspace. The Access Dashboard then gives the operator a copy-ready prompt for Codex so the installing shell can keep the owned workspace key for retries, future login shells, alternate MCP clients, and quota upgrades.

Open MCP controls
Mental stream
sync → commit → graph

Use `sync` to reload the current indexed external memory snapshot, then `commit` to create a time node linked to themes, aspects, briefing points, facets, and recurring threads in the Memory Journal graph. When `occurred_at` is provided, the server inserts the slice into the correct previous/next temporal slot automatically.

Open Memory Journal

What The Download Includes

The bundle should feel complete when it lands on disk: plugin manifest, hosted MCP endpoint, sigil-led visuals, packaged skills, install docs, and the marketplace template that shortens setup.

Bundle contents

Plugin shell plus hosted MCP config

The zip includes the Codex plugin manifest, the hosted Syndu MCP endpoint definition, investigation skills, validation scripts, and install docs.

.codex-plugin/plugin.json .mcp.json Bundled skills Smoke test and validator
Marketplace template

Fastest tested local install

The download includes a ready-to-edit marketplace template. The plugin should live inside the workspace and the marketplace path should stay relative, which is the shape Codex accepted in the install test.

{
  "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 Reopen Plugins if needed Install from Plugins tab
Connection contract

Approve in browser, create the shell key in the Access Dashboard

The recommended flow is to let Codex trigger the browser approval step, then create the MCP key in the Access Dashboard and copy the follow-up Codex prompt for the shell you are actually installing.

Browser approval identifies the workspace The Access Dashboard opens to MCP credentials Paste the Access Dashboard prompt back into the active shell
Memory validation

Sync, commit, and inspect the graph

The reinstall should end with a visible memory proof: Codex syncs the latest external snapshot, writes a commit bundle, and sends the operator into the Memory Journal to inspect the new graph slice.

Run sync in the configured shell Create one commit bundle Inspect the Memory Journal graph
What users get

Investigate, explain, and remember

Once installed, Codex can resolve risky identifiers, explain contextual risk, find related entities, preserve approved outcomes in governed workspace memory, and collaborate through share-safe hive intelligence.

Cyber and fraud workflows Governed workspace memory Approved hive reuse

Why Start With The Codex Plugin

This is the fastest public path into Syndu's shared risk memory product: download one bundle, install it locally, connect the workspace, then investigate and preserve outcomes without building any middleware.

Codex plugin

A visible product surface, not a hidden integration

A dedicated Codex plugin page gives Syndu Web LTD a real installation surface, not just an MCP endpoint buried inside deeper documentation. Visitors can understand the product, download it immediately, and install it with a tested local marketplace pattern.

Codex plugin

The plugin is the product surface

The plugin packages Syndu as a buyer-facing product, not just a technical connector. It gives Codex one place to investigate outside-in risk context, preserve governed workspace memory, and reuse share-safe intelligence across future agent work.

Codex plugin

Browser approval should feel like onboarding, not friction

The first live connect should not leave the buyer stranded on a callback page. Syndu now uses the browser approval step to identify the workspace and then opens the Access Dashboard directly to the MCP credentials panel so the user can finish the Codex setup without hunting through the site.

Codex plugin

The installing shell gets the credential it will actually use

The important shell state is the workspace MCP key created in the Access Dashboard. The Access Dashboard should hand the user a copy-ready Codex prompt that configures the exact session they are in, then optionally persists the same key into `~/.zprofile` for future login shells.

Codex plugin

The memory loop should be visible, not mystical

After reinstall, the operator should be able to tell Codex to `sync` the latest external snapshot, then `commit` a new time slice and open the Memory Journal. That commit should appear as a central time node with linked themes, aspects, briefing points, facets, and recurring threads so the shared mental stream is inspectable instead of hidden.

Codex plugin

Quota exhaustion should lead back into provisioning, not a dead end

When the workspace runs out of metered investigation quota, Syndu should return a direct Access Dashboard link to the MCP plans and subscription controls. That keeps the user inside one clear flow: investigate, hit the limit, provision more quota, and continue from the same workspace.

Codex plugin

Organizational memory, hive collaboration, and shared intelligence

The plugin is not just a lookup shim. It is how Codex reaches Syndu's governed memory layer so analysts and agents can preserve approved outcomes inside one workspace, promote share-safe findings into the hive, and benefit from Syndu's shared threat intelligence in the next investigation.

Codex plugin

Live community demand increases investigative confidence

The Codex plugin now carries Syndu's 10-minute queryability layer into the investigation. When repeated public lookups and multiple requester IPs converge on the same entity, Codex can show that live attention pattern beside the report-backed score and the saved workspace outcome.

Open The Right Surface

A cold visitor should be able to move from the download into the right follow-on surface without hunting through the rest of the site.

Current zip

Download plugin

syndu-v0.1.13-codex-plugin.zip

Download the current installable plugin bundle directly from Syndu.

Stable bundle name Local plugin install Current published version
Open document
Access Dashboard

Provision workspace access

/access/?mode=mcp#mcp-credentials

Create the account, manage the workspace, and provision the MCP key that the installing Codex shell should keep after the browser approval step from the Syndu workspace Access Dashboard.

Sign up or sign in Create MCP credential Copy prompt for Codex
Open document
Product surface

Read the MCP server page

/pages/resources/mcp-server/

See the hosted MCP endpoint, tool surface, pricing ladder, and governed memory model that sit behind the plugin.

Hosted endpoint Tool catalog MCP pricing and governance
Open document
Use cases

Explore Codex-ready workflows

/pages/resources/mcp-use-cases/

Jump into the buyer workflows that make the plugin easy to understand: IP and domain investigation, detection drafting, and fraud review.

Cyber investigation Detection drafting Fraud and account-abuse review
Open document

Recommended Connection Paths

The public plugin should prefer the lightest credible install path, while still leaving room for power-user operation.

Recommended

Browser approval plus Access Dashboard key creation

Best for real customer installs because Codex can narrate the handoff, Syndu can open the Access Dashboard to the right MCP controls, and the user finishes with a copy-ready prompt for the shell they care about.

Shell knows the browser handoff is coming The Access Dashboard opens to the MCP panel Best fit for first-time plugin installs
Optional fallback

Pre-existing MCP key

Best for scripts, raw MCP clients, smoke tests, and operators who already created the key in the Access Dashboard and simply want to export it into the shell before Codex ever asks.

Provision in the Access Dashboard Export SYNDU_MCP_TOKEN Useful for direct MCP troubleshooting
Product value

Governed memory and hive reuse

Install is only the first step. The real buyer value is that Codex can carry approved findings forward instead of repeating the same first investigation every time.

Workspace memory is included Approved hive sharing is governed Cyber and fraud workflows stay in one loop

Download, Install, Connect

This is the tested install sequence for someone discovering Syndu on the public website and wanting the plugin workspace to stay ready after the browser handoff.

01

Download the current bundle

Grab the latest Syndu Codex plugin zip from this page so the buyer starts from a packaged local plugin rather than raw docs or repo instructions.

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` and stays local to the environment you are configuring.

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`. Codex rejected absolute local plugin paths in the install rehearsal.

04

Install Syndu in the Plugins tab

Open the Plugins tab, switch to the Syndu Local marketplace, and install Syndu just like any other local plugin bundle. If the marketplace does not appear immediately, reopen the tab or restart Codex once.

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, accept terms if needed, and connect the workspace cleanly.

06

Use the Access Dashboard to mint the shell credential

After approval, Syndu opens the Access Dashboard directly to the MCP credential panel. Create the key there, copy the follow-up Codex prompt into the same shell, and let Codex set `SYNDU_MCP_TOKEN` for the current shell or future login shells.

07

Run sync, then commit, then inspect memory

After the shell is configured, use `sync` to reload the current external memory snapshot, then ask Codex to write a `commit` bundle. Open the Memory Journal to inspect the time node, connected themes, aspects, briefing points, and recurring threads.

08

Retry the first live request

Once the shell has the key, the first real Syndu tool call can proceed without the user having to rediscover the control plane or guess what the plugin expects next.

09

If the daily budget is exhausted, return to the Access Dashboard and provision more quota

Syndu should surface a direct Access Dashboard link to `/access/?mode=mcp&reason=quota#plans` so Codex can tell the user exactly where to go next, while memory lookup and writeback remain available.

Copy-Ready Install Snippets

Give operators the fewest moving parts possible: download, unpack, add marketplace metadata, let Codex narrate the browser handoff, then finish the shell setup in the Access Dashboard with a copy-ready prompt for Codex.

bash

Download and unpack locally

mkdir -p ./plugins ./.agents/plugins
curl -L -o syndu-v0.1.13-codex-plugin.zip "https://syndu.com/pages/resources/codex-plugin/download/"
unzip -o syndu-v0.1.13-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 paste the Access Dashboard prompt into Codex

Codex, run codex mcp login syndu if needed, wait for me to finish browser approval, then tell me when to open the Access Dashboard and copy the follow-up MCP key prompt for this shell.

Related Resources

Documentation

Syndu Documentation Index

Syndu gives computer-using agents outside-in risk context and a governed memory loop. This index maps the supporting docs: plugin install, 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