OpenVibeCoding/docs/index.html at aa28d3d29198e9bb2d3cbd12d3ad9be9d6c3fb69 · xiaojiou176-open/OpenVibeCoding · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
<!doctype html>
<html lang="en">
  <head>
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <title>CortexPilot | AI Work Command Tower for Codex, Claude Code, and MCP</title>
    <meta
      name="description"
      content="CortexPilot is the AI Work Command Tower for Codex and Claude Code workflows with Model Context Protocol (MCP)-readable runs, Workflow Cases, proof and replay, and a compatibility-first adoption path for OpenClaw, skills, and builders."
    />
    <meta
      name="keywords"
      content="CortexPilot, Codex, Claude Code, OpenClaw, MCP, Model Context Protocol, AI workflow, command tower, Workflow Cases, proof and replay, operator copilot, compatibility matrix, skills, builders"
    />
    <link rel="canonical" href="https://xiaojiou176-open.github.io/CortexPilot-public/" />
    <meta property="og:title" content="CortexPilot | AI Work Command Tower for Codex, Claude Code, and MCP" />
    <meta
      property="og:description"
      content="AI Work Command Tower for Codex and Claude Code workflows with public first-run cases, governed agents, Model Context Protocol (MCP)-readable runs, proof, replay, and a compatibility-first path for OpenClaw, skills, and builders."
    />
    <meta property="og:type" content="website" />
    <meta property="og:url" content="https://xiaojiou176-open.github.io/CortexPilot-public/" />
    <meta property="og:image" content="./assets/storefront/social-preview-1280x640.png" />
    <meta name="twitter:card" content="summary_large_image" />
    <meta name="twitter:title" content="CortexPilot | AI Work Command Tower for Codex, Claude Code, and MCP" />
    <meta
      name="twitter:description"
      content="AI Work Command Tower for Codex and Claude Code workflows with public first-run cases, governed agents, Model Context Protocol (MCP)-readable runs, proof, replay, and a compatibility-first path for OpenClaw, skills, and builders."
    />
    <meta name="twitter:image" content="./assets/storefront/social-preview-1280x640.png" />
    <script type="application/ld+json">
      {
        "@context": "https://schema.org",
        "@type": "WebSite",
        "name": "CortexPilot",
        "url": "https://xiaojiou176-open.github.io/CortexPilot-public/",
        "description": "AI Work Command Tower for Codex and Claude Code workflows with read-only Model Context Protocol (MCP), Workflow Cases, proof and replay, and explainable operator guidance.",
        "keywords": [
          "Codex",
          "Claude Code",
          "OpenClaw",
          "MCP",
          "AI workflow",
          "command tower",
          "operator copilot",
          "compatibility matrix",
          "skills",
          "builders"
        ]
      }
    </script>
    <script type="application/ld+json">
      {
        "@context": "https://schema.org",
        "@type": "FAQPage",
        "mainEntity": [
          {
            "@type": "Question",
            "name": "Is CortexPilot an official Codex or Claude Code plugin?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "No. Codex now has official plugin surfaces and OpenClaw has official plugin and skills surfaces, but CortexPilot currently ships workflow-aligned integrations, repo-owned skills, read-only MCP, and local bundle examples rather than a published listing."
            }
          },
          {
            "@type": "Question",
            "name": "Is the public MCP surface write-capable?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "No. CortexPilot's current public MCP contract is read-only, and write-capable mutation remains outside the public promise."
            }
          },
          {
            "@type": "Question",
            "name": "Where does OpenClaw fit today?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "OpenClaw stays in the adjacent coding-agent layer. New teams should use the compatibility matrix, integration guide, and repo-owned skills path before implying a shipped native plugin."
            }
          },
          {
            "@type": "Question",
            "name": "What should a new team open first?",
            "acceptedAnswer": {
              "@type": "Answer",
              "text": "Start with the compatibility matrix if the main question is which adoption path fits your stack. Then choose read-only MCP, skills, builders, or the first success path based on the real job."
            }
          }
        ]
      }
    </script>
    <style>
      :root {
        --bg: #f5f0e8;
        --paper: #fffaf2;
        --ink: #17232c;
        --muted: #4f616e;
        --accent: #9f4c26;
        --accent-dark: #234056;
        --line: #d8ccbb;
      }

      * { box-sizing: border-box; }

      body {
        margin: 0;
        font-family: "Trebuchet MS", Verdana, sans-serif;
        color: var(--ink);
        background:
          radial-gradient(circle at 10% 15%, rgba(203, 115, 73, 0.18), transparent 22%),
          radial-gradient(circle at 85% 10%, rgba(35, 64, 86, 0.14), transparent 18%),
          linear-gradient(180deg, #f7f2ea 0%, #efe6d8 100%);
      }

      main {
        max-width: 1100px;
        margin: 0 auto;
        padding: 56px 24px 88px;
      }

      .hero {
        display: grid;
        gap: 28px;
      }

      .eyebrow {
        display: inline-block;
        padding: 8px 14px;
        border-radius: 999px;
        background: rgba(35, 64, 86, 0.08);
        color: var(--accent-dark);
        font-size: 14px;
        font-weight: 700;
        letter-spacing: 0.02em;
      }

      h1 {
        margin: 0;
        font-family: Georgia, "Times New Roman", serif;
        font-size: clamp(40px, 7vw, 68px);
        line-height: 1.05;
      }

      .lede {
        max-width: 850px;
        margin: 0;
        color: var(--muted);
        font-size: clamp(20px, 2.5vw, 26px);
        line-height: 1.5;
      }

      .actions {
        display: flex;
        flex-wrap: wrap;
        gap: 14px;
      }

      .mini-nav {
        display: flex;
        flex-wrap: wrap;
        gap: 12px;
      }

      .mini-nav a {
        color: var(--accent-dark);
        text-decoration: none;
        font-size: 14px;
        font-weight: 700;
      }

      .mini-nav a:hover,
      .mini-nav a:focus-visible {
        text-decoration: underline;
        text-underline-offset: 2px;
      }

      .mini-nav a:focus-visible {
        outline: 2px solid var(--accent-dark);
        outline-offset: 2px;
      }

      .actions a {
        text-decoration: none;
        border-radius: 999px;
        padding: 14px 20px;
        font-weight: 700;
      }

      .actions .primary {
        background: var(--accent);
        color: white;
      }

      .actions .secondary {
        background: rgba(35, 64, 86, 0.08);
        color: var(--accent-dark);
      }

      .panel,
      .grid-card {
        background: rgba(255, 250, 242, 0.9);
        border: 1px solid var(--line);
        border-radius: 26px;
      }

      .panel {
        padding: 24px;
      }

      .hero-image {
        width: 100%;
        border-radius: 22px;
        border: 1px solid var(--line);
        background: white;
      }

      .caption {
        margin: 10px 0 0;
        color: var(--muted);
        font-size: 15px;
      }

      .section {
        margin-top: 44px;
      }

      .section h2 {
        font-family: Georgia, "Times New Roman", serif;
        font-size: 32px;
        margin: 0 0 14px;
      }

      .grid {
        display: grid;
        gap: 18px;
        grid-template-columns: repeat(auto-fit, minmax(220px, 1fr));
      }

      .grid-card {
        padding: 20px;
      }

      .grid-card h3 {
        margin-top: 0;
        font-size: 19px;
      }

      .grid-card p,
      .section p,
      .section li {
        color: var(--muted);
        line-height: 1.65;
      }

      code {
        background: rgba(35, 64, 86, 0.08);
        padding: 2px 6px;
        border-radius: 6px;
        font-family: "SFMono-Regular", "Menlo", monospace;
        color: var(--accent-dark);
      }
    </style>
  </head>
  <body>
    <main>
      <section class="hero">
        <span class="eyebrow">Public landing source for CortexPilot</span>
        <nav class="mini-nav" aria-label="Top navigation">
          <a href="./use-cases/">First proven workflow</a>
          <a href="./compatibility/">Compatibility matrix</a>
          <a href="./builders/">Builder quickstart</a>
          <a href="https://github.com/xiaojiou176-open/CortexPilot-public">Repository</a>
          <a href="https://github.com/xiaojiou176-open/CortexPilot-public/releases">Releases</a>
        </nav>
        <h1>Command Tower for Codex and Claude Code workflows.</h1>
        <p class="lede">
          Start with one proven workflow, confirm the Workflow Case, then inspect Proof &amp; Replay.
          CortexPilot gives Codex- and Claude Code-style teams one governed operator path instead
          of scattered prompts, local scripts, and after-the-fact logs.
        </p>
        <p class="caption">
          Current boundary: this is a repo-backed operator control plane, not a hosted product, and the
          shipped MCP surface remains read-only.
        </p>
        <div class="actions">
          <a class="primary" href="./use-cases/">See the first proven workflow</a>
          <a class="secondary" href="./compatibility/">Choose the right adoption path</a>
        </div>
        <p class="caption">
          After those two doors, go deeper through
          <a href="./agent-starters/"> agent starter kits</a>,
          <a href="./mcp/"> read-only MCP</a>,
          <a href="./integrations/"> integrations</a>,
          <a href="./skills/"> skills</a>,
          <a href="./ai-surfaces/"> AI + MCP + API surfaces</a>, or the
          <a href="./ecosystem/"> ecosystem map</a>.
        </p>

        <div class="panel">
          <img
            class="hero-image"
            src="./assets/storefront/hero-command-tower.svg"
            alt="CortexPilot flow from PM request to Command Tower to evidence and replay"
          />
          <p class="caption">
            The public story should stay simple: send one request, watch it move through Command Tower,
            confirm the Workflow Case, then inspect Proof &amp; Replay before you trust the result.
          </p>
        </div>
      </section>

      <section class="section">
        <h2>Why teams take CortexPilot seriously</h2>
        <div class="grid">
          <article class="grid-card">
            <h3>One governed first loop</h3>
            <p>It is not just “the model replied.” The same first loop keeps the request, case record, proof, and replay on one operator path.</p>
          </article>
          <article class="grid-card">
            <h3>Share-ready Workflow Cases</h3>
            <p>The strongest public slice is not a screenshot alone. It is the Workflow Case recap that lets other people review what happened without re-running the whole stack.</p>
          </article>
          <article class="grid-card">
            <h3>Truthful boundary language</h3>
            <p>CortexPilot explicitly says what is proven, what is still a showcase path, and what remains read-only or live-verified later.</p>
          </article>
        </div>
      </section>

      <section class="section">
        <h2>FAQ</h2>
        <div class="grid">
          <article class="grid-card">
            <h3>Is CortexPilot an official Codex or Claude Code plugin?</h3>
            <p>Not today. Codex now has official plugin surfaces and OpenClaw has official plugin and skills surfaces, but CortexPilot currently ships workflow-aligned integrations, repo-owned skills, read-only MCP, and local bundle examples rather than a published listing.</p>
          </article>
          <article class="grid-card">
            <h3>Is the public MCP surface write-capable?</h3>
            <p>CortexPilot's current public MCP contract is read-only, and write-capable mutation remains outside the public promise.</p>
          </article>
          <article class="grid-card">
            <h3>Where does OpenClaw fit today?</h3>
            <p>OpenClaw stays in the adjacent coding-agent layer. New teams should use the compatibility matrix, integration guide, and repo-owned skills path before implying a shipped native plugin.</p>
          </article>
          <article class="grid-card">
            <h3>What should a new team open first?</h3>
            <p>Start with the compatibility matrix if the main question is which adoption path fits your stack. Then choose read-only MCP, skills, builders, or the first success path based on the real job.</p>
          </article>
        </div>
      </section>

      <section class="section">
        <h2>Choose your path</h2>
        <p>
          New here? Keep the first decision simple: start with one proven workflow, choose the right adoption path,
          then open deeper protocol or builder pages only after the job is clear.
        </p>
        <div class="grid">
          <article class="grid-card">
            <h3>I want one proven workflow first</h3>
            <p>Start here if you want the shortest honest story: one public baseline, one proof pack, and one share-ready Workflow Case recap before you read internals.</p>
            <p><a href="./use-cases/">Open the first proven workflow</a></p>
          </article>
          <article class="grid-card">
            <h3>I need the adoption path</h3>
            <p>Start here if your real question is “I use Codex, Claude Code, OpenClaw, skills, or builders. Which CortexPilot surface should I open first?”</p>
            <p><a href="./compatibility/">Open the compatibility matrix</a></p>
          </article>
          <article class="grid-card">
            <h3>I build on protocols or packages</h3>
            <p>Start here once the boundary is clear and you need read-only MCP, OpenAPI, contract-facing types, or the thin builder surfaces.</p>
            <p><a href="./mcp/">Open read-only MCP</a> · <a href="./api/">Open API quickstart</a> · <a href="./builders/">Open builder quickstart</a></p>
          </article>
        </div>
        <p class="caption">
          Need exact starter files? Open <a href="./agent-starters/">agent starter kits</a>. Need the truthful Codex / Claude Code / OpenClaw map?
          Open <a href="./integrations/">integrations</a>. Need repo-owned playbooks? Open <a href="./skills/">skills quickstart</a>.
          Need the broader market framing? Open the <a href="./ecosystem/">ecosystem map</a>.
        </p>
      </section>

      <section class="section">
        <h2>The product spine</h2>
        <div class="grid">
          <article class="grid-card">
            <h3>Command Tower</h3>
            <p>Watch governed agents, MCP tools, queue state, and live operator signals from one surface.</p>
          </article>
          <article class="grid-card">
            <h3>Workflow Cases</h3>
            <p>Keep the request, queue, verdict, linked runs, and operating context attached to one case record.</p>
          </article>
          <article class="grid-card">
            <h3>Proof &amp; Replay</h3>
            <p>Inspect failures, compare reruns, and keep the execution chain auditable before you trust the outcome.</p>
          </article>
        </div>
        <p class="caption">
          Read-only MCP and the AI operator brief sit on top of this spine as inspection layers, not as second execution truths.
        </p>
      </section>

      <section class="section">
        <h2>First proven workflow</h2>
        <p>
          The shortest honest start is still repo-local. The host-compatible path stays:
        </p>
        <ol>
          <li><code>npm run bootstrap:host</code></li>
          <li><code>CORTEXPILOT_HOST_COMPAT=1 bash scripts/test_quick.sh --no-related</code></li>
          <li><code>npm run dashboard:dev</code></li>
        </ol>
        <p class="caption">
          In practice, a clean first pass should take about 5-10 minutes and end with four visible signals:
          one request created from PM, one case visible in Command Tower, one Workflow Case you can confirm,
          and one Proof &amp; Replay surface you can inspect before trusting the result.
        </p>
        <p class="caption">
          Official first public path: start with <code>news_digest</code> if you want the smallest release-proven
          proof loop. Treat <code>topic_brief</code> and <code>page_brief</code> as showcase expansions, not equally
          proven baselines.
        </p>
        <div class="grid">
          <article class="grid-card">
            <h3>news_digest</h3>
            <p>Best for the fastest proof-oriented first run with one topic, a few domains, and a short time window.</p>
            <p><strong>Proof state:</strong> official public baseline.</p>
          </article>
          <article class="grid-card">
            <h3>topic_brief</h3>
            <p>Best for a bounded topic brief when you want search-backed evidence without broadening scope.</p>
            <p><strong>Proof state:</strong> public showcase, not yet equally release-proven.</p>
          </article>
          <article class="grid-card">
            <h3>page_brief</h3>
            <p>Best for a single URL with browser-backed evidence and a read-only workflow case wrapper.</p>
            <p><strong>Proof state:</strong> public showcase, browser-backed path.</p>
          </article>
        </div>
        <p class="caption">
          See the full proof pack, benchmark summary, and share-ready Workflow Case recap in
          <a href="./use-cases/"> the first proven workflow guide</a>.
        </p>
      </section>
    </main>
  </body>
</html>