Skip to content

Record why Grok and Copilot CLI get no harness entry - #11

Merged
UnbreakableMJ merged 1 commit into
mainfrom
verify-grok-copilot
Aug 25, 2026
Merged

Record why Grok and Copilot CLI get no harness entry#11
UnbreakableMJ merged 1 commit into
mainfrom
verify-grok-copilot

Conversation

@UnbreakableMJ

Copy link
Copy Markdown
Contributor

Both were candidates for the harness table after the Kimi/Qwen survey. Neither should be added, and the reasons are worth writing down before someone re-derives them wrongly.

Grok already has engram's commands

Grok reads other vendors' directories on purpose. From its own bundled docs/user-guide/08-skills.md:

Location Tier
~/.grok/skills/, ~/.grok/commands/ User
~/.claude/skills/, ~/.claude/commands/ User — Claude Code compatibility
~/.cursor/skills/ User — Cursor compatibility

And 05-configuration.md: "Every cell defaults to true."

Verified non-interactively with grok inspect:

Skills (79)
  └ engram-context      user [claude]
  └ engram-ingest       user [claude]
  └ engram-save-chat    user [claude]
MCP Servers (14)
  └ engram (stdio)      config

Engram's Claude Code install already serves Grok, on both surfaces. A Grok entry would write a second copy that Grok's own name-deduplication would shadow. Its own ~/.grok/skills is a home-manager symlink into the store here anyway.

Copilot CLI takes plugins, not files

$ copilot plugin --help
  install [options] <source>   Install a plugin
… from plugin marketplaces, GitHub repositories, repository subdirectories, or direct git URLs.

There is no directory engram can drop a command into. The previous reason — "no user-writable command or prompt directory" — invited exactly the wrong follow-up: this machine does have ~/.copilot/skills, but it is a symlink belonging to the user's own skills bundle, not to Copilot. Reading it as a surface would have shipped commands nothing loads — the Codex prompts/ mistake a second time. The detail now says what Copilot actually accepts.

Also surveyed, no change warranted

Finding
Pi 0.80.6, bundled with Orca. No MCP registration, no command surface, all three session dirs empty — configured but unused.
Oh-My-Pi Not installed. (omp on PATH is oh-my-posh 16.0.10.)
VS Code engram registered in ~/.config/Code/User/mcp.json; prompts/ exists but is empty. A real surface — but an editor, not a CLI harness. Scope decision, not a defect.
Cursor skills-cursor/ is vendor-shipped (Grok filters these as vendor defaults); no user ~/.cursor/skills, no engram MCP registration.
Cline 3.0.46, but ~/.cline/data/settings does not exist — never configured. Its skills come from npx skills, not a directory.

Gates

fmt · clippy -D warnings · 257 tests · REUSE 3.3 · makeinfo clean

🤖 Generated with Claude Code

https://claude.ai/code/session_016i16R4GhdSffsboRYq97Fs

Both were candidates for the harness table. Neither should be added, and the
reasons are worth writing down before someone re-derives them wrongly.

Grok already has engram's commands. It reads other vendors' directories on
purpose: `[compat.claude]` in `~/.grok/config.toml` defaults every cell to
`true`, so `~/.claude/commands/` and `~/.claude/skills/` are scanned as
user-tier sources. `grok inspect` lists engram-context, engram-ingest and
engram-save-chat as `user [claude]`, and `engram (stdio)` under MCP Servers —
so engram's Claude Code install already serves Grok, and a Grok entry would
write a second copy that Grok's own name-deduplication would shadow.

Copilot CLI takes plugins, not files. `copilot plugin install` accepts a
marketplace, a GitHub repository, or a git URL; there is no directory engram
can drop a command into. Its previous one-line reason said only that there was
no writable directory, which invited exactly the wrong follow-up: this machine
has a `~/.copilot/skills` symlink, but it belongs to the user's own skills
bundle rather than to Copilot, and reading it as a surface would have shipped
commands nothing loads — the Codex prompts mistake again.

Gates: fmt, clippy -D warnings, 257 tests, REUSE 3.3, makeinfo clean.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016i16R4GhdSffsboRYq97Fs
@UnbreakableMJ
UnbreakableMJ merged commit 6bd2dee into main Aug 25, 2026
5 checks passed
@UnbreakableMJ
UnbreakableMJ deleted the verify-grok-copilot branch August 25, 2026 10:29

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8369b0d4eb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread AGENTS.md
Comment on lines +273 to +276
- **Grok needs no harness entry, and adding one would duplicate its commands.**
Grok reads other vendors' directories on purpose: `[compat.claude]` in
`~/.grok/config.toml` defaults every cell to `true`, so `~/.claude/commands/`
and `~/.claude/skills/` are scanned as user-tier sources, as are

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Add a path for Grok-only installations

For a user who has Grok but not Claude Code, this premise fails: Harness::ALL has no Grok entry, while install skips Claude Code when its ~/.claude probe is absent, so nothing creates commands in any directory Grok scans. The cited grok inspect result only demonstrates a machine where Claude commands already exist. Add a detected Grok surface or otherwise arrange a Claude-compatible target; without one, Grok-only users cannot install these commands despite this paragraph saying no entry is needed.

AGENTS.md reference: AGENTS.md:L180-L180

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant