gray-area
v0.14.0Trajectory evidence for Special Circumstances: what a session actually did, as against what it reported. Captures each seat's own transcript by path at SubagentStop, and reads it back with provenance on every row — so an inspection cites the primary record rather than a summary of it.
By Gregory BlockLicense: MIT3 GitHub starsUpdated 6 days ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 3 skill or MCP entries
- Source updated
- Sep 18, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install gray-area for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install gray-area@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/ctoforaday/special-circumstancesClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/gray-area/.
Plugin files
├── .claude-plugin/plugin.json├── skills/elicitation-testing/SKILL.md├── skills/restart-recovery/SKILL.md└── skills/telepathy/SKILL.md
Included Skills3
When an agent or seat did something you cannot explain from its instructions — a rule it read and did not apply, a command run twice, a duty skipped — gather what it actually did with telepathy, then interview a tool-less fork of its own session about why, and adjudicate the answer against the record. One of the first things to reach for when diagnosing agent behaviour.
After a host restart, crash or shutdown cut off running Claude sessions, use this to find them with `telepathy agents --lost` and bring each back in the mode it had — through a running Remote Control server first, then by reattach or local resume, one session at a time and only the ones the human chooses.
Before asking a peer agent what happened, or assuming nobody else is working on a file, use `telepathy` to query the host-wide trajectory catalogue — it answers from what agents DID rather than from what they remember.
Plugin manifests1
{
"name": "gray-area",
"displayName": "Gray Area",
"version": "0.14.0",
"description": "Trajectory evidence for Special Circumstances: what a session actually did, as against what it reported. Captures each seat's own transcript by path at SubagentStop, and reads it back with provenance on every row — so an inspection cites the primary record rather than a summary of it.",
"author": {
"name": "Gregory Block"
},
"license": "MIT",
"keywords": [
"trajectory",
"adversarial",
"audit",
"adjudication",
"agent-evaluation"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[gray-area on Agent Plugins Marketplace](https://pluginsmp.com/plugins/gray-area)