pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for shaft-mcp

Pod holds 23 of 239 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to shaft-mcp.

Most discussed

Tracking: restore local ChaosEngine health and harden installer

Tracking

  • #5352 installer reliability (Python 3.11, MCP cwd, durable marketplace, stale cleanup, doctor probes)
  • Phase 2 local installation recovery (after #5352 merge)
  • #5353 installer UX (whole-install ETA, stalled transfer, success CTA, JSON stdout, next-session readiness)
  • Phase 4 final proof, recovery report, Learning Session

Owner-selected validation: balanced. Terminal adversarial review: enabled, max two rounds. One writer at a time. Second issue starts from merg

Read the thread · 2026-08-25 · closed · outside contributor · 8 comments

Tracking: First-class Grok support in SHAFT MCP installer, CLI, IntelliJ plugin, and Autobot

Tracking

  • #5100 Installer target grok + contract lock (Phase 1)
  • #5101 IntelliJ Assistant route + setup (Phase 2) — PR #5110
  • #5102 Autobot / LocalAgent GROK (Phase 3) — PR #5111
  • #5103 shaft_project_init_agents loop grok (Phase 4) — PR #5113
  • #5104 Remaining enumerations + companion docs (Phase 5) — docs PR ShaftHQ/shafthq.github.io#987

Close this tracker only when Phases 1-5 are on main and the docs PR is opened.

Objective

Make Grok (Grok Build TUI and th

Read the thread · 2026-08-17 · closed · outside contributor · 7 comments

Ship a portable ChaosEngine runtime in the act-as-mohab plugin

Related to #4726.

Ship the canonical ChaosEngine repository operations as a deterministic, client-neutral runtime inside the portable act-as-mohab Agent Plugin. The archive must run from any repository without embedding a SHAFT checkout path.

Acceptance summary:

  • Assemble bin/act-as-mohab.pyz from tracked canonical modules only.
  • Add plugin-root .mcp.json; the Codex manifest references it as ./.mcp.json.
  • Expose repository-context, watch-pr-checks, checkpoint-status, and mcp

Read the thread · 2026-08-11 · closed · outside contributor · 8 comments

[Feature Request]: Agent Plugin Development

Decision summary Adopt the Agent Plugins v1.0.0 package format as the portability floor. Build two independently versioned, skills-first packages: 1. act-as-mohab — the maintainer workflow plugin, owned with the canonical harness. 2. shaft-skills — the SHAFT test-authoring/user plugin, owned with SHAFT-facing guidance. Keep the portable core small and client-neutral. Preserve host lifecycle hooks, trust configuration, installers, user-local secrets, caches, and UI behavior as explicit

Read the thread · 2026-08-06 · closed · outside contributor · 5 comments

Automated, source-controlled IntelliJ+SHAFT capture demo recording (headed, AI-driven)

Goal

A repeatable, source-controlled procedure (and the AI-driven tooling to execute it) for recording a real, headed demo of SHAFT's IntelliJ plugin capture/codegen workflow:

  1. Launch a sandboxed IntelliJ instance (shaft-intellij via gradlew runIde) with a simple, resettable Selenium+TestNG demo project open.
  2. Install/verify the SHAFT plugin's setup flow (runtime + shaft-mcp + skills), including the "optional upgrade to use SHAFT" step.
  3. Ask the plugin's Assistant to start a

Read the thread · 2026-07-27 · closed · outside contributor · 11 comments

[BLOCKED UPSTREAM - DO NOT RE-DISPATCH] [Bug] [Tooling] memory secret-scanner unanchored openai_api_key rule hard-blocks the store

Hit while running the mandatory session-entry-point memory load for the #3996 investigation.

Symptom

memory load "<task>" and memory search "<query>" return nothing usable. memory load ends with:

error: MemoryIndexUnavailable: Canonical files are invalid; SQLite index was not replaced.

memory search "swipeElementIntoView" and memory search "Flutter" both returned No matching Memory. — not "no results for this query", but a dead index. AGENTS.md ("Memory & Learning

Read the thread · 2026-07-25 · closed · outside contributor · 8 comments

Tracking: SHAFT tool architecture sweep — minimal deterministic toolset, cached catalog, deterministic IntelliJ selector, skills router

Owner-mandated architecture sweep of the SHAFT CLI + MCP tool surface and the agent harness around it. Design doc frozen in-session (adversarially reviewed); headline decisions:

  • Trim shaft-mcp from 164 → 89 tools via an ActiveEngine dispatcher (one element_click, one element_type, one browser_*/capture_* family dispatching across Selenium/Appium/Playwright; recording-wrapper aware).
  • Delete intent-based act tools (natural_act, mobile_natural_act); keep deterministic `capture_

Read the thread · 2026-07-20 · closed · outside contributor · 12 comments

gbrain doctor: low brain_score (45/100) and reranker auth failures (ZEROENTROPY_API_KEY)

What happened

While tuning tools/agent-infra/gbrain-autosync.cmd for PR #3707, I ran gbrain run_doctor (via the gbrain MCP tool) as part of verifying the sync-throughput change. It surfaced two items outside that PR's scope:

  1. brain_score: FAIL, 45/100 — needs its own investigation into what's dragging the score down (likely stale/unconsolidated facts, orphaned pages, or embedding coverage gaps — not diagnosed yet).
  2. reranker_health: WARN, 2 auth failures — the reranker s

Read the thread · 2026-07-17 · closed · outside contributor · 5 comments

Most recent

Create correlated redactable execution evidence bundles

User Scenarios & Testing

Given a failed local or CI test, a developer can open one correlated evidence bundle containing bounded browser, framework, network, console, screenshot, and agent-action context without exposing credentials or unrelated data.

Edge Cases

Secret-bearing headers, request bodies, PII, oversized artifacts, successful runs, partial capture, unsupported browsers, retention expiry, and cross-machine replay must be explicit.

Functional Requirements

  • FR-1: Define o

Read the thread · 2026-08-28 · open · outside contributor · 0 comments

Add a governed agentic test workflow

User Scenarios & Testing

Given a deterministic seed and requested user journey, an agent can plan, generate, run, diagnose, and propose a test change through bounded, inspectable phases.

Edge Cases

Prompt injection, untrusted page content, credentials, destructive browser actions, runaway retries, inconsistent seeds, unavailable tools, and model disagreement must fail closed.

Functional Requirements

  • FR-1: Separate planner, generator, runner, diagnoser, and proposal responsibiliti

Read the thread · 2026-08-28 · open · outside contributor · 1 comment

Expose IntelliJ agent readiness and trust context

Subtask of #5437.

Enhance the existing agent picker and summary using only current settings/provider metadata. Show readiness/authentication state plus agent, mode, access, and attached context. Keep advanced controls behind Run settings at narrow widths.

Acceptance: unknown facts say Not configured; mutation approval and external-provider/access context remain explicit; focused layout and settings tests pass.

Read the thread · 2026-08-28 · closed · outside contributor · 2 comments

[Feature Request]: Deploy on dockhold option

Proposal

Hi! I noticed SHAFT MCP already supports remote deployment through Render, Fly.io and Smithery.

I'm building Dockhold, an EU-hosted PaaS focused heavily on always-on services and remote MCP servers. It handles the deployment, HTTPS and restarts, and apps don't sleep between MCP calls.

Dockhold: https://dockhold.eu Docs: https://dockhold.eu/docs

SHAFT MCP looks like a really good fit. Would you be open to me sending a small PR adding Dockhold as another deployment option?

Read the thread · 2026-08-27 · open · external user · 0 comments

Memory schema rejects canonical objects (facets, scope, type)

Problem

python3 .chaos-engine/tool.py memory check and the shaft-memory MCP query fail with MemorySchemaValidationFailed. Ordinary Memory search/save is unusable.

Evidence

Observed 2026-08-26 on checkout bcdef992 (dirty ChaosEngine/fix-codex-hook-json). Representative errors:

  • .memory/memory/architecture.json /facets: additional property not allowed
  • .memory/memory/architecture.json /scope: additional property not allowed
  • .memory/memory/architecture.json /type:

Read the thread · 2026-08-26 · closed · outside contributor · 0 comments

Recover managed runtimes and Memory MCP initialization

Subtask of #5395.

Scope

Make installer diagnostics identify sealed-generation executable drift, atomically replace unhealthy generations without weakening integrity, remove duplicate MCP registrations, and prove real initialize/initialized/tools-list exchange with protocol-clean stdout.

Delivery

Implemented sequentially in the grouped draft pull request.

Read the thread · 2026-08-26 · closed · outside contributor · 0 comments

ChaosEngine installer: add idempotency, preservation, MCP, and live acceptance coverage

Subtask of #5362. Depends on every implementation child.

Objective

Provide consolidated regression and live acceptance proving upstream-native installation is idempotent, preserves user data/configuration, and starts all required MCPs and hooks in a fresh client session.

Required automated coverage

  1. Resolver: stable selection, prerelease/yanked rejection, compatibility, offline reuse, corrupt executable, missing sibling command, and action classification.
  2. Platforms: apt, dnf, Wind

Read the thread · 2026-08-25 · closed · outside contributor · 0 comments

ChaosEngine installer: expose dependency, MCP, and hook health in status/doctor

Subtask of #5362. Depends on resolver, prerequisite, tool, MCP, and hook contracts.

Objective

Make ChaosEngine status and doctor output explain dependency freshness, current-folder readiness, MCP health, hook trust, and required restart actions without leaking machine secrets.

Structured contract

For each dependency/component expose deterministic fields for installed/resolved version, provider, executable reachability, account scope, selected action, compatibility, freshness verificati

Read the thread · 2026-08-25 · closed · outside contributor · 0 comments

ChaosEngine installer: reconcile canonical MCP servers and plugin Node discovery

Subtask of #5362. Depends on Python tools, JavaScript tools, Maven Tools, and platform prerequisite children.

Objective

Generate one canonical, path-stable MCP definition per ChaosEngine service and repair Node discovery for official plugin MCP servers without modifying third-party plugin source.

Required server state

  • Memory: one canonical server using the resolved absolute memory-mcp executable and verified project cwd.
  • MemPalace: one canonical server using the resolved absolute

Read the thread · 2026-08-25 · closed · outside contributor · 0 comments

ChaosEngine installer: adopt upstream-native Maven Tools MCP setup

Subtask of #5362. Depends on resolver and Temurin prerequisite children.

Objective

Replace private Maven Tools MCP/Temurin provisioning with the upstream-supported latest stable native JAR flow while preserving an explicitly selected Docker alternative.

Required upstream flow

For a missing, unhealthy, or outdated native installation:

git clone --branch <resolved-stable-tag> --depth 1 https://github.com/arvindand/maven-tools-mcp.git <user-cache-staging>
cd <user-cache-staging>

[Read the thread](https://github.com/ShaftHQ/SHAFT_ENGINE/issues/5367) · 2026-08-25 · closed · outside contributor · 0 comments

### ChaosEngine installer: set up current-folder Memory and remote Context7

Subtask of #5362. Depends on resolver and Node/npm prerequisite children.

## Objective

Install latest stable Memory and Context7 CLI for the invoking user, initialize Memory in the current repository, and remove Context7's runtime dependency on local npx for MCP startup.

## Required commands and configuration

```bash
npm install -g @aictx/memory@latest   # only missing/outdated
memory init --no-view                 # only uninitialized current project
npm install -g ctx7@latest            # 

[Read the thread](https://github.com/ShaftHQ/SHAFT_ENGINE/issues/5366) · 2026-08-25 · closed · outside contributor · 0 comments

### Tracking: Use upstream-native dependency setup and repair ChaosEngine MCP/hooks

# Problem statement

ChaosEngine currently provisions private runtime archives and writes overlapping MCP entries. On a user account where `node`, `npm`, `npx`, `java`, or `uv` is not on `PATH`, Codex reports startup failures for `context7`, `mempalace`, `creative_production_mcp`, `codex-security`, and `shaft-memory`. The present installation can contain healthy private binaries while ordinary shell commands and plugin-owned launchers still cannot find them. Project hooks may also be current on 

[Read the thread](https://github.com/ShaftHQ/SHAFT_ENGINE/issues/5362) · 2026-08-25 · closed · outside contributor · 2 comments

### [Feature Request]: chaos-engine installer minor UX tweaks

As seen from the below output, there are some enhancements to be made:
- the E in the chaos engine logo doesn't look like an E. enhance it to look like a real inverted E.
- the Trace section should show more details, we agreed before to have some scrollable details and to research online to reuse an existing installer library if it makes sense or add any dependencies as needed without messing up the main section of the UI.
- the section after the trace should have a title similar to the trace se

[Read the thread](https://github.com/ShaftHQ/SHAFT_ENGINE/issues/5359) · 2026-08-25 · closed · outside contributor · 1 comment

### [Bug]: chaos-engine installer

running this command on LINUX MINT

curl -fsSL "https://raw.githubusercontent.com/ShaftHQ/SHAFT_ENGINE/main/chaos-engine/install.sh" | bash -s -- "https://raw.githubusercontent.com/ShaftHQ/SHAFT_ENGINE/main/chaos-engine/install.sh"

provides this console output

/=====. +--+ / | |==| / | * / |==| / | |==| / +=====/ +--+ / Chaos Engine Installing ChaosEngine into /media/mohab/OS/Users/Mohab/IdeaProjects/SHAFT_EN

Read the thread · 2026-08-24 · closed · outside contributor · 1 comment

[Bug]: chaos-engine install fails on Windows: memory-mcp entrypoint probe runs POSIX shell shim through node.exe

Summary

On Windows, the chaos-engine bootstrap installer deterministically fails during "Provision dependencies" with:

memory-mcp entrypoint probe failed
ChaosEngine bootstrap failed with exit 1

This is 100% reproducible, not transient/antivirus-related, and rolls back cleanly each time.

Environment

Read the thread · 2026-08-24 · closed · external user · 1 comment

The remaining reports are on the project's issue tracker.