@metaharness/copilot 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 rUv
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,72 @@
+# MetaHarness × VSCode/Copilot mcp.json
+
+A minimal scaffold that wires up GitHub Copilot in VSCode with MCP (Model Context Protocol) servers via `mcp.json`. This is for developers who already use Copilot Chat in VSCode and want to extend it with custom tools, file-system context, and MCP-backed integrations without hand-rolling configuration files. It does NOT ship a custom Copilot model, agent runtime, or replacement for Copilot Chat — it just generates the config layer that VSCode's Copilot reads on startup.
+
+## Quickstart
+
+```bash
+npx @metaharness/copilot@latest my-bot
+cd my-bot && npm install && harness doctor
+```
+
+Then open `my-bot/` in VSCode. Copilot Chat will detect `mcp.json` and offer to enable the configured servers on first launch.
+
+## What you get
+
+- `.vscode/mcp.json` — Copilot-compatible MCP server registry with sensible defaults (filesystem, fetch, memory)
+- `.github/copilot-instructions.md` — repo-scoped instructions Copilot Chat reads automatically
+- `harness.config.json` — MetaHarness manifest declaring the host, template, and validation rules
+- `package.json` with `harness` CLI wired up for doctor/validate/sync workflows
+- `agents/` directory with one starter agent definition and a README on how to add more
+- `.gitignore` and `.vscodeignore` tuned for MCP server logs and local secrets
+
+## Advanced
+
+Run the built-in health check after scaffolding to confirm Copilot can see the config:
+
+```bash
+$ harness doctor
+[ok] VSCode detected (1.95.0+)
+[ok] .vscode/mcp.json valid (3 servers declared)
+[ok] copilot-instructions.md present
+[ok] node >= 20
+```
+
+Validate your `mcp.json` against the Copilot schema before committing:
+
+```bash
+$ harness validate --strict
+validating .vscode/mcp.json...
+  servers.filesystem    ok
+  servers.fetch         ok
+  servers.memory        ok
+all checks passed
+```
+
+Inspect the resolved config that Copilot will actually load (useful when diagnosing why a server is silently disabled):
+
+```bash
+$ harness sync --dry-run
+would write: .vscode/mcp.json
+would write: .github/copilot-instructions.md
+no changes (config in sync)
+```
+
+## FAQ
+
+**Q: Do I need a Copilot subscription for this?**
+A: Yes — this scaffolds config for the Copilot Chat extension in VSCode, which requires an active GitHub Copilot subscription. The scaffold itself is free.
+
+**Q: Will this work with Copilot in JetBrains or Neovim?**
+A: Not directly. The `.vscode/mcp.json` format is VSCode-specific. JetBrains uses a different MCP integration path; pick a different host template for that.
+
+**Q: Can I commit `.vscode/mcp.json` to a shared repo?**
+A: Yes, and it's recommended for team consistency. Keep secrets out of it — use `${env:VAR}` substitution and document the required env vars in `copilot-instructions.md`.
+
+## License
+
+MIT. Built on metaharness (https://www.npmjs.com/package/metaharness).
+
+## Deep-dive
+
+Full explainer gist: https://gist.github.com/ruvnet/532201b1e66c528df87857002a1c0ad9

package/bin/scaffold.mjs

@@ -0,0 +1,21 @@
+#!/usr/bin/env node
+import { execSync } from 'node:child_process';
+import process from 'node:process';
+
+const args = process.argv.slice(2);
+const name = args[0] && !args[0].startsWith('--') ? args[0] : 'my-bot';
+const extra = (args[0] === name ? args.slice(1) : args).join(' ');
+
+const cmd = `npx --yes metaharness@latest ${name} --template minimal --host copilot --force${extra ? ' ' + extra : ''}`;
+
+try {
+  execSync(cmd, { stdio: 'inherit' });
+  console.log('');
+  console.log(`Next steps:`);
+  console.log(`  cd ${name} && npm install`);
+  console.log(`  harness doctor   # verify VSCode + mcp.json are wired up`);
+  console.log(`  code .           # open in VSCode and enable Copilot MCP servers`);
+} catch (err) {
+  console.error(`metaharness scaffold failed: ${err.message}`);
+  process.exit(err.status || 1);
+}

package/package.json

@@ -0,0 +1,40 @@
+{
+  "name": "@metaharness/copilot",
+  "version": "0.1.0",
+  "description": "MetaHarness example — VSCode/Copilot mcp.json scaffold for agentic workflows (npx @metaharness/copilot my-bot)",
+  "homepage": "https://github.com/ruvnet/agent-harness-generator/tree/main/examples-packages/copilot",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/ruvnet/agent-harness-generator.git",
+    "directory": "examples-packages/copilot"
+  },
+  "license": "MIT",
+  "author": "rUv <ruv@ruv.net>",
+  "type": "module",
+  "bin": "./bin/scaffold.mjs",
+  "files": [
+    "bin/**",
+    "README.md",
+    "LICENSE"
+  ],
+  "scripts": {
+    "smoke": "node --check bin/scaffold.mjs"
+  },
+  "keywords": [
+    "metaharness",
+    "agent-harness",
+    "agent-harness-generator",
+    "copilot",
+    "host",
+    "ai-agent",
+    "mcp",
+    "npx",
+    "scaffold"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "engines": {
+    "node": ">=20.0.0"
+  }
+}