CodexPluginStats
← SeismicCONTENT HISTORY

Update to Seismic

Snapshot Nov 14, 2026 · 00:13 UTC · version 1.0.0

WHAT CHANGED

Package or technical metadata updated

Package or technical metadata updated

Observed in package metadata. These changes alone do not establish a new customer-facing feature.

Save Seismic and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

These are saved file metadata. Open a changed file to read its text edits.

Package file

Before

Sep 30, 2026 · 22:48 UTC

62f420f5858103db10d2497c66386f32975fc01557f0e7caa64cfbace7018fe3

After

Nov 14, 2026 · 00:13 UTC

b49c404851d7851a0e0fc585b50267a71868508ce5e9b0e31a6dfaeef5b68e7f

Package file

Before

Sep 30, 2026 · 22:48 UTC

2547

After

Nov 14, 2026 · 00:13 UTC

2531

Compare saved observations

Download comparison JSON

Changed files

Choose a file to see its text changes. Binary or large files show metadata only.

.codex-plugin/plugin.json →

.codex-plugin/plugin.json

− removed · + added

--- before
+++ after
@@ -6,7 +6,7 @@
   "description": "The Seismic MCP Connector for ChatGPT enables secure integration between ChatGPT and Seismic, allowing ChatGPT to generate accurate, Seismic-specific responses using approved sales and enablement content.\n\nBuilt on the Model Context Protocol (MCP), the connector provides authentication and scope-based access control, ensuring only authorized tools and content are available within ChatGPT.\n\nTo configure access, users must install the MCP Connector for ChatGPT app from Seismic Exchange, where tenant admins define scopes and permissions that control which Seismic capabilities are exposed.\n\nOnce configured:\n\nChatGPT connects to Seismic through the MCP server\n\nOnly approved tools and content are accessible\n\nResponses are grounded in trusted, compliant materials\n\nWithout proper installation and scope configuration, Seismic tools will not be visible in ChatGPT.",
   "interface": {
     "capabilities": [],
-    "category": "Business & Operations",
+    "category": "Sales",
     "defaultPrompt": [
       "What are the best practices for sellers?",
       "Generate a LiveSend link for B2 case study document"
Full technical diff · 2 changed fields

changed /files/.codex-plugin~1plugin.json/sha256

BEFORE
"62f420f5858103db10d2497c66386f32975fc01557f0e7caa64cfbace7018fe3"
AFTER
"b49c404851d7851a0e0fc585b50267a71868508ce5e9b0e31a6dfaeef5b68e7f"

changed /files/.codex-plugin~1plugin.json/size

BEFORE
2547
AFTER
2531
Full snapshot data
{
  "files": {
    ".app.json": {
      "sha256": "b4936b0211cc48300a9d657587d872be185bdaf0c2d7ab32c3cb9879d8d6747f",
      "size": 127
    },
    ".codex-plugin/plugin.json": {
      "sha256": "b49c404851d7851a0e0fc585b50267a71868508ce5e9b0e31a6dfaeef5b68e7f",
      "size": 2531
    }
  }
}

SHA-256 of public snapshot: 714a802b4dbcf1687757872070a650b83fb45c952b3b4f424d3c91004dbbe434