Update to Stele

Changed files

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

.app.json →

.codex-plugin/plugin.json →

assets/avatar.png →

mcp.json →

plugin.json →

skills/stele/SKILL.md →

plugin.json

− removed · + added

--- before
+++ after
@@ -0,0 +1,102 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "app-6a594b32d24881918d24f7855d68c4a4",
+  "version": "3.0.0",
+  "description": "Share persistent project memory and task tracking across AI agents.",
+  "author": {
+    "name": "Stele AI LLC",
+    "url": "https://stele-ai.dev"
+  },
+  "homepage": "https://stele-ai.dev",
+  "keywords": [
+    "project memory",
+    "knowledge graph",
+    "task tracking"
+  ],
+  "extensions": {
+    "com.openai": {
+      "interface": {
+        "displayName": "Stele",
+        "shortDescription": "Share memory across AI agents",
+        "longDescription": "Stele gives project teams a shared, persistent knowledge graph and task system. Open a visual project board, recall decisions and lessons, inspect provenance, capture durable knowledge, and coordinate claimed work across your connected tools.",
+        "developerName": "Stele AI LLC",
+        "category": "Developer Tools",
+        "capabilities": [
+          "Recall project context",
+          "Track tasks",
+          "Trace decisions",
+          "Show project boards"
+        ],
+        "websiteURL": "https://stele-ai.dev",
+        "supportURL": "https://stele-ai.dev/support",
+        "privacyPolicyURL": "https://stele-ai.dev/privacy",
+        "termsOfServiceURL": "https://stele-ai.dev/terms",
+        "defaultPrompt": [
+          "Open my Stele project board and show me the open tasks worth doing next.",
+          "Save the decision we just made, including why we chose it and what it changes.",
+          "Create and claim a task for the implementation work we agreed on, with clear success criteria."
+        ],
+        "composerIcon": "./assets/avatar.png",
+        "logo": "./assets/avatar.png"
+      },
+      "onboardingSkill": "./skills/stele/SKILL.md",
+      "review": {
+        "test_cases": {
+          "positive": [
+            {
+              "description": "Recall the decision and lesson relevant to a project question.",
+              "prompt": "In the openai-review Stele project, what do we know about checkout retries? Summarize the decision and the lesson that supports it.",
+              "tools_triggered": "recall",
+              "expected_behavior": "Returns a concise, evidence-based summary citing the matching decision and lesson by Stele ID and title without inventing missing facts."
+            },
+            {
+              "description": "Open the project board and show a task card in the conversation.",
+              "prompt": "Open the openai-review project board beside our conversation, then show me the Ship retry telemetry task as a card with its linked context.",
+              "tools_triggered": "open_project_board, show_node",
+              "expected_behavior": "Opens the project board beside the conversation and renders a card for Ship retry telemetry with its status, priority, body, and linked retry decision. Do not show unrelated project data."
+            },
+            {
+              "description": "Capture a project decision with its rationale and topics.",
+              "prompt": "In openai-review, record this decision: Cap payment retries at five attempts. The reason is to bound queue pressure during provider incidents. Tag it payments and retries.",
+              "tools_triggered": "knowledge",
+              "expected_behavior": "Creates one decision knowledge node and confirms its new KNOW-N ID, title, category, rationale, and topics."
+            },
+            {
+              "description": "Create and atomically claim a task through the task lifecycle.",
+              "prompt": "In openai-review, create a P1 task called Add retry-attempt dashboard with success criteria that operations can see attempts and final outcomes, then claim it.",
+              "tools_triggered": "task",
+              "expected_behavior": "Creates one P1 TASK-N with the requested success criteria and leaves it in progress with the authenticated claimant recorded."
+            },
+            {
+              "description": "Trace the recorded provenance behind a project decision.",
+              "prompt": "Trace why checkout retries use exponential backoff in openai-review. Show the causal or linked path and distinguish recorded facts from your inference.",
+              "tools_triggered": "inspect",
+              "expected_behavior": "Returns a short evidence-backed path using Stele IDs and clearly labels any inference that is not directly recorded."
+            }
+          ],
+          "negative": [
+            {
+              "description": "Do not trigger Stele for an unrelated calendar request.",
+              "prompt": "What meetings do I have tomorrow?"
+            },
+            {
+              "description": "Do not trigger Stele for standalone code generation with no memory or tracking request.",
+              "prompt": "Write a Python implementation of quicksort."
+            },
+            {
+              "description": "Do not trigger Stele for an unrelated email action.",
+              "prompt": "Send the team an email confirming tomorrow's lunch reservation."
+            }
+          ]
+        },
+        "demo_recording_url": "https://stele-ai.dev/demo.mp4",
+        "commerce": false,
+        "commerce_description": "Stele does not sell products or process payments through this plugin."
+      },
+      "publication": {
+        "release_notes": "Stele now opens a project board beside the conversation and a full project view in the sidebar. Task lists render as a board, and individual tasks, knowledge, and documents can appear as cards with linked context and provenance. The board pages longer task lists. The hosted skill now tells agents when to show these views. Hosted onboarding has a clearer first-project path, and the MCP server handles authorization-server outages more accurately. Every tool that writes is now marked open-world, because a write to a public project is readable by anyone, and the Timeline tool is part of the reviewed set."
+      },
+      "apps": "./.app.json"
+    }
+  }
+}