-
Notifications
You must be signed in to change notification settings - Fork 29
Expand file tree
/
Copy pathindex.html
More file actions
508 lines (494 loc) · 24.1 KB
/
index.html
File metadata and controls
508 lines (494 loc) · 24.1 KB
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
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>CortexPilot | Coding-agent integrations for Codex, Claude Code, and OpenClaw</title>
<meta
name="description"
content="Truthful CortexPilot integration guide for Codex, Claude Code, and OpenClaw: read-only MCP, API/client entrypoints, repo-owned skills, and the current no-fake-plugin boundary."
/>
<meta
name="keywords"
content="CortexPilot, Codex, Claude Code, OpenClaw, coding agent integrations, MCP, plugin, skills, workflow cases, proof and replay"
/>
<link rel="canonical" href="https://xiaojiou176-open.github.io/CortexPilot-public/integrations/" />
<meta property="og:title" content="CortexPilot | Coding-agent integrations for Codex, Claude Code, and OpenClaw" />
<meta
property="og:description"
content="Truthful integration map for Codex, Claude Code, and OpenClaw with read-only MCP, API/client entrypoints, repo-owned skills, and no fake official-plugin claims."
/>
<meta property="og:type" content="article" />
<meta property="og:url" content="https://xiaojiou176-open.github.io/CortexPilot-public/integrations/" />
<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 | Coding-agent integrations for Codex, Claude Code, and OpenClaw" />
<meta
name="twitter:description"
content="Truthful integration map for Codex, Claude Code, and OpenClaw with read-only MCP, API/client entrypoints, repo-owned skills, and no fake official-plugin claims."
/>
<meta name="twitter:image" content="../assets/storefront/social-preview-1280x640.png" />
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "TechArticle",
"headline": "CortexPilot coding-agent integrations for Codex, Claude Code, and OpenClaw",
"url": "https://xiaojiou176-open.github.io/CortexPilot-public/integrations/",
"description": "Truthful integration guide for Codex, Claude Code, and OpenClaw using read-only MCP, repo-owned skills, and current API or builder entrypoints."
}
</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 compatibility, read-only MCP, repo-owned skills, builder entrypoints, and local bundle examples rather than a published listing."
}
},
{
"@type": "Question",
"name": "Where does OpenClaw fit today?",
"acceptedAnswer": {
"@type": "Answer",
"text": "OpenClaw stays in the adjacent coding-agent layer. CortexPilot can still provide read-only MCP, proof and replay, and skill-pack guidance around it without claiming a first-class native plugin."
}
},
{
"@type": "Question",
"name": "Should a new team start from MCP, builders, or skills?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Start from read-only MCP when the first need is protocol inspection, from builders or API when the first need is package-level integration, and from skills when the first need is repeatable operating playbooks."
}
},
{
"@type": "Question",
"name": "Does this page mean CortexPilot is hosted or write-capable through MCP?",
"acceptedAnswer": {
"@type": "Answer",
"text": "No. The current public MCP contract is read-only, and CortexPilot should not be described as a hosted operator product today."
}
}
]
}
</script>
<style>
:root {
color-scheme: light;
--bg: #f5f2eb;
--panel: #fffdf9;
--ink: #17232c;
--muted: #52616d;
--line: rgba(23, 35, 44, 0.12);
--accent: #155e75;
--accent-soft: rgba(21, 94, 117, 0.1);
--warn: #92400e;
--warn-soft: rgba(146, 64, 14, 0.1);
--shadow: 0 24px 60px rgba(23, 35, 44, 0.1);
}
* { box-sizing: border-box; }
body {
margin: 0;
background:
radial-gradient(circle at top left, rgba(21, 94, 117, 0.08), transparent 32%),
linear-gradient(180deg, #f9f6ef 0%, #f1ece4 100%);
color: var(--ink);
font: 16px/1.65 "Inter", "Segoe UI", system-ui, sans-serif;
}
main {
max-width: 1080px;
margin: 0 auto;
padding: 40px 20px 72px;
}
a { color: var(--accent); }
a:hover { color: #0f4d60; }
.hero, .section, .table-shell {
background: var(--panel);
border: 1px solid var(--line);
border-radius: 28px;
box-shadow: var(--shadow);
}
.hero, .section { padding: 28px; }
.hero { display: grid; gap: 18px; }
.eyebrow, .badge {
display: inline-flex;
width: fit-content;
padding: 7px 12px;
border-radius: 999px;
font-size: 13px;
font-weight: 700;
}
.eyebrow { background: rgba(23, 35, 44, 0.08); color: var(--muted); }
.badge.primary { background: var(--accent-soft); color: var(--accent); }
.badge.warn { background: var(--warn-soft); color: var(--warn); }
h1, h2, h3 { margin: 0; line-height: 1.15; }
h1 { font-size: clamp(2.4rem, 4vw, 3.8rem); max-width: 12ch; }
h2 { font-size: 1.6rem; margin-bottom: 12px; }
p, li, td { color: var(--muted); }
.lede { font-size: 1.08rem; max-width: 76ch; }
.actions, .mini-nav { display: flex; flex-wrap: wrap; gap: 12px; }
.button {
display: inline-flex;
align-items: center;
justify-content: center;
padding: 12px 16px;
border-radius: 999px;
text-decoration: none;
font-weight: 600;
}
.button.primary { background: var(--accent); color: white; }
.button.secondary {
border: 1px solid var(--line);
background: white;
color: var(--ink);
}
.section { margin-top: 24px; }
.grid {
display: grid;
grid-template-columns: repeat(auto-fit, minmax(230px, 1fr));
gap: 16px;
}
.card {
border: 1px solid var(--line);
border-radius: 22px;
background: white;
padding: 18px;
}
.table-shell { margin-top: 24px; overflow: hidden; }
table { width: 100%; border-collapse: collapse; }
th, td {
padding: 14px 16px;
border-bottom: 1px solid var(--line);
text-align: left;
vertical-align: top;
}
th {
font-size: 13px;
letter-spacing: 0.03em;
text-transform: uppercase;
background: rgba(23, 35, 44, 0.04);
}
tr:last-child td { border-bottom: none; }
code {
background: rgba(23, 35, 44, 0.06);
border-radius: 6px;
padding: 2px 6px;
font-family: "SFMono-Regular", Menlo, monospace;
}
</style>
</head>
<body>
<main>
<section class="hero">
<span class="eyebrow">Coding-agent integration guide</span>
<nav class="mini-nav" aria-label="Top navigation">
<a href="../">Back to the public landing page</a>
<a href="../ecosystem/">Ecosystem map</a>
<a href="../compatibility/">Compatibility matrix</a>
<a href="../agent-starters/">Agent starter kits</a>
<a href="../ai-surfaces/">AI + MCP + API surfaces</a>
<a href="../skills/">Skills quickstart</a>
</nav>
<h1>Codex, Claude Code, and OpenClaw integrations.</h1>
<p class="lede">
CortexPilot already fits into modern coding-agent workflows, but the truthful entrypoint is
<strong>not</strong> “install our official plugin.” The truthful story today is:
<strong>read-only MCP</strong>, <strong>repo-owned skills</strong>, <strong>API/client entrypoints</strong>,
and <strong>Workflow Cases + Proof & Replay</strong> as the common operating record.
</p>
<p class="lede">
Use this page when you want the shortest honest answer to: “How do I actually use CortexPilot with
Codex, Claude Code, or OpenClaw right now?”
</p>
<p class="lede">
The safe product positioning is <strong>workflow-aligned</strong> and <strong>read-only MCP-compatible</strong>.
Codex now has official plugin surfaces, Claude Code currently exposes project-level MCP / hooks / subagent surfaces,
and OpenClaw already has plugin + skills hosts of its own. Keep <strong>plugin</strong> wording narrow:
for CortexPilot, the default public story is still integrations + skills + MCP plus local bundle examples, not a published listing.
</p>
<div class="actions">
<a class="button primary" href="../mcp/">Open read-only MCP quickstart</a>
<a class="button secondary" href="../compatibility/">Open compatibility matrix</a>
<a class="button secondary" href="../agent-starters/">Open agent starter kits</a>
<a class="button secondary" href="../builders/">Open builder quickstart</a>
<a class="button secondary" href="../skills/">Open skills quickstart</a>
<a class="button secondary" href="https://github.com/xiaojiou176-open/CortexPilot-public/blob/main/README.md">Open repository README</a>
</div>
<p class="lede">
Need the fastest proof-first walkthrough instead of the deeper integration map?
<a href="../use-cases/">See the first proven workflow</a>.
</p>
</section>
<section class="section">
<h2>The shortest truthful compatibility map</h2>
<div class="table-shell">
<table>
<thead>
<tr>
<th>Surface</th>
<th>Works today</th>
<th>How CortexPilot fits</th>
<th>What we must not claim</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Codex</strong></td>
<td>Yes</td>
<td>Command Tower, Workflow Cases, Proof & Replay, read-only MCP, repo-owned skills, and API/client entrypoints all fit Codex-style governed coding loops.</td>
<td>Do not call CortexPilot a published Codex directory entry or an OpenAI-managed integration surface.</td>
</tr>
<tr>
<td><strong>Claude Code</strong></td>
<td>Yes</td>
<td>The same repo-owned surfaces work for Claude Code workflows: read-only inspection, case tracking, operator guidance, and package-level builder glue.</td>
<td>Do not imply an official Claude Code plugin, Anthropic-managed partnership, or hosted account integration.</td>
</tr>
<tr>
<td><strong>OpenClaw</strong></td>
<td>Bundle-compatible only when explicitly mapped</td>
<td>OpenClaw belongs in the adjacent coding-agent layer. CortexPilot can still provide read-only MCP, skill-pack guidance, and proof/case review surfaces around it without pretending the same first-class binding as Codex / Claude Code.</td>
<td>Do not present OpenClaw support as an official plugin, native OpenClaw plugin, or first-class product binding unless a real mapped bundle or native plugin ships and is tested.</td>
</tr>
</tbody>
</table>
</div>
</section>
<section class="section">
<h2>Official ecosystem reality anchors</h2>
<div class="grid">
<article class="card">
<span class="badge primary">Codex</span>
<h3>Native surfaces that already exist</h3>
<p>
Start from the official
<a href="https://github.com/openai/codex">openai/codex repo</a>,
the <a href="https://developers.openai.com/codex">Codex docs</a>,
and the <a href="https://developers.openai.com/codex/ide">IDE install path</a>.
</p>
<p>
CortexPilot should wrap Codex workflows with Command Tower, Workflow Cases,
Proof & Replay, read-only MCP, and repo-owned skills or local bundle examples.
It should not be framed as a published Codex directory entry or an OpenAI-managed surface.
</p>
</article>
<article class="card">
<span class="badge primary">Claude Code</span>
<h3>Native surfaces that already exist</h3>
<p>
Start from the official
<a href="https://code.claude.com/docs/en/overview">Claude Code overview</a>
and the
<a href="https://code.claude.com/docs/en/mcp">Claude Code MCP docs</a>.
</p>
<p>
CortexPilot should fit as the governed review/proof/control-plane layer around
those workflows. It should not be framed as a Claude Code marketplace listing
or Anthropic-managed plugin surface.
</p>
</article>
<article class="card">
<span class="badge warn">OpenClaw</span>
<h3>Native surfaces that already exist</h3>
<p>
Start from the official
<a href="https://github.com/openclaw/openclaw">OpenClaw repo</a>,
the <a href="https://docs.openclaw.ai/tools/skills">skills docs</a>,
and the <a href="https://github.com/openclaw/clawhub">ClawHub registry/catalog</a>.
</p>
<p>
OpenClaw already has its own skills and plugin/catalog reality. CortexPilot should
therefore land on the integration, proof, replay, and read-only MCP side first,
not pretend it already ships a native OpenClaw plugin.
</p>
</article>
</div>
</section>
<section class="section">
<h2>Current distribution status by platform</h2>
<div class="table-shell">
<table>
<thead>
<tr>
<th>Platform</th>
<th>Official surface exists?</th>
<th>Current CortexPilot state</th>
<th>Do not overclaim</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Codex</strong></td>
<td>Yes. Official plugins surface exists.</td>
<td>Public starter docs, one local marketplace example, and one portable local bundle exist. There is still no official Codex listing receipt tracked here today.</td>
<td>Do not say CortexPilot is listed in an OpenAI-managed directory unless you have the listing URL or receipt.</td>
</tr>
<tr>
<td><strong>Claude Code</strong></td>
<td>Yes. Official marketplace, submit, and review flow exist.</td>
<td>Public starter docs and a local <code>--plugin-dir</code> bundle seed exist. The OpenHands submission is filed separately, but there is still no Claude marketplace submission receipt tracked here today.</td>
<td>Do not say <code>submitted</code>, <code>in review</code>, or <code>live</code> without the matching official receipt.</td>
</tr>
<tr>
<td><strong>OpenClaw</strong></td>
<td>Yes. Official ClawHub registry exists.</td>
<td>Public starter docs plus a compatible local bundle path exist. The matching adoption-router skill is live on ClawHub.</td>
<td>Do not say <code>in review</code> for OpenClaw. Its official model is publish-first, not review-queue-first.</td>
</tr>
</tbody>
</table>
</div>
<p>
Need the exact starter files next? Open the
<a href="../agent-starters/">agent starter kits</a>.
Need the proof assets that show the public loop is real? Open the
<a href="../use-cases/">public use-case guide</a>.
</p>
</section>
<section class="section">
<h2>What teams can actually adopt today</h2>
<ul>
<li><strong>Command Tower</strong> as the single operator surface above coding-agent runs</li>
<li><strong>Workflow Cases</strong> as the shared operating record that ties request, queue, verdict, and linked runs together</li>
<li><strong>Proof & Replay</strong> as the review surface you use before trusting an outcome</li>
<li><strong>read-only MCP</strong> when you want machine-readable inspection without mutation</li>
<li><strong>frontend client + contract + shared UI substrate</strong> when you want repo-owned builder entrypoints</li>
<li><strong>repo-local skills</strong> when you want coding agents to use the same operating playbook</li>
</ul>
</section>
<section class="section">
<h2>Fastest adoption ladder by ecosystem</h2>
<div class="table-shell">
<table>
<thead>
<tr>
<th>Ecosystem</th>
<th>Start here</th>
<th>Then use CortexPilot for</th>
<th>Stop sign</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Codex</strong></td>
<td>Codex CLI / IDE docs</td>
<td>Compatibility matrix → read-only MCP or proof-first use case → builder starter if package reuse is needed</td>
<td>Do not call CortexPilot a published Codex directory entry.</td>
</tr>
<tr>
<td><strong>Claude Code</strong></td>
<td>Claude Code overview + MCP docs</td>
<td>Compatibility matrix → repo-owned skills + read-only MCP → builder starter for workspace reuse</td>
<td>Do not imply a plugin marketplace or hosted account integration.</td>
</tr>
<tr>
<td><strong>OpenClaw</strong></td>
<td>OpenClaw repo + skills docs + ClawHub</td>
<td>Use CortexPilot as the adjacent review/proof/read-only MCP layer, then map packages or skills only when a concrete workflow really needs them</td>
<td>Do not present CortexPilot as a native OpenClaw plugin unless a mapped path is shipped and tested.</td>
</tr>
</tbody>
</table>
</div>
</section>
<section class="section">
<h2>Three copy-paste starting points</h2>
<p>
If your team wants something more concrete than “read the docs,” start with one of these repo-owned paths.
</p>
<pre><code># 1) protocol-first: prove the read-only MCP surface is real
bash scripts/run_readonly_mcp.sh
# 2) builder-first: prove the thin client + contract bootstrap path is real
node packages/frontend-api-client/examples/control_plane_starter.local.mjs \
--base-url http://127.0.0.1:10000 \
--role WORKER \
--mutation-role TECH_LEAD \
--preview-provider cliproxyapi \
--preview-model gpt-5.4
# 3) proof-first: prove the public first-run loop is real
CORTEXPILOT_HOST_COMPAT=1 bash scripts/test_quick.sh --no-related</code></pre>
<p>
Need the client-specific setup files after that? Open the
<a href="../agent-starters/">agent starter kits</a> for tracked Codex
<code>config.toml</code>, Claude Code <code>.mcp.json</code>, and
OpenClaw <code>openclaw mcp set</code> starter objects.
</p>
</section>
<section class="section">
<h2>Portable drop-in recipe for coding-agent teams</h2>
<p>
If your real question is “What do I actually hand to Codex, Claude Code, or OpenClaw maintainers this afternoon?”,
keep the recipe small and honest:
</p>
<ol>
<li>Vendor the repo truth you want the agent to follow: <code>README.md</code>, <code>docs/README.md</code>, <code>AGENTS.md</code>, and the specific skill folders you actually plan to reuse.</li>
<li>Wire the repo-owned MCP server as a <strong>stdio command</strong>, not as a hosted claim: <code>bash /absolute/path/to/CortexPilot/scripts/run_readonly_mcp.sh</code>.</li>
<li>Choose only one adoption lane first: protocol-first, skills-first, or builder-first. Do not promise plugin/store support unless a real platform surface exists and is verified.</li>
</ol>
<pre><code># 1) keep the repo truth close to the agent
sed -n '1,220p' README.md
sed -n '1,220p' docs/README.md
sed -n '1,220p' AGENTS.md
# 2) keep MCP on the truthful stdio path
bash /absolute/path/to/CortexPilot/scripts/run_readonly_mcp.sh
# 3) keep builder adoption copy-pasteable
node packages/frontend-api-client/examples/control_plane_starter.local.mjs \
--base-url http://127.0.0.1:10000 \
--role WORKER \
--mutation-role TECH_LEAD \
--preview-provider cliproxyapi \
--preview-model gpt-5.4</code></pre>
<p>
OpenClaw teams should use the same three lanes as an <strong>adaptation recipe</strong>, not as proof of a first-class native plugin.
</p>
</section>
<section class="section">
<h2>How to talk about this truthfully</h2>
<div class="grid">
<article class="card">
<h3>Good wording</h3>
<p>“CortexPilot works with Codex and Claude Code workflows through Workflow Cases, Proof & Replay, read-only MCP, repo-owned skills, and builder entrypoints.”</p>
</article>
<article class="card">
<h3>Bad wording</h3>
<p>“CortexPilot already ships the official Codex / Claude Code / OpenClaw listing.”</p>
</article>
<article class="card">
<h3>Good wording</h3>
<p>“OpenClaw stays in the adjacent coding-agent layer and can use CortexPilot as a bundle-compatible review surface when the mapped path is explicitly shipped and tested.”</p>
</article>
<article class="card">
<h3>Bad wording</h3>
<p>“OpenClaw is a first-class officially supported plugin surface inside CortexPilot today.”</p>
</article>
</div>
</section>
<section class="section">
<h2>FAQ</h2>
<div class="grid">
<article class="card">
<h3>Is this an official Codex or Claude Code plugin page?</h3>
<p>No. Codex now has official plugin surfaces and OpenClaw has official plugin and skills surfaces, but CortexPilot currently ships workflow compatibility, read-only MCP, repo-owned skills, builder entrypoints, and local bundle examples rather than a published listing.</p>
</article>
<article class="card">
<h3>Where does OpenClaw fit today?</h3>
<p>OpenClaw stays in the adjacent coding-agent layer. CortexPilot can still provide read-only MCP, proof and replay, and skill-pack guidance around it without claiming a first-class native plugin.</p>
</article>
<article class="card">
<h3>Should a new team start from MCP, builders, or skills?</h3>
<p>Start from read-only MCP when the first need is protocol inspection, from builders or API when the first need is package-level integration, and from skills when the first need is repeatable operating playbooks.</p>
</article>
<article class="card">
<h3>Does this page mean CortexPilot is hosted or write-capable through MCP?</h3>
<p>No. The current public MCP contract is read-only, and CortexPilot should not be described as a hosted operator product today.</p>
</article>
</div>
</section>
</main>
</body>
</html>