context-harness
Related Servers
Alternatives to context-harness
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to enforce spec-driven development and verify code before it is marked done, using six tools that catch invented APIs, scan for hallucinated content, check plugin conformance, sandbox-run tests, validate schemas, and record audit evidence.771 npm8PolyForm Noncommercial 1.0.0
- AlicenseAqualityBmaintenanceZero-dependency token optimizer, test-failure triage gate, and System 1.5 semantic guardrail for AI coding agents. Intercepts compiler errors, missing dependencies, and doom loops in < 500µs.697 PyPI12MIT
- AlicenseAqualityBmaintenanceEnables AI agents to run a project's pytest, unittest, jest, or vitest suites and get back compact structured results with trimmed tracebacks, collection errors kept apart from real failures, and the slowest tests. Agents can then re-run just the failures, expand one failure with local variables, repeatedly execute a single test to judge flakiness, and inspect Python coverage gaps, all under a hard timeout that kills the whole process tree.7MIT
- AlicenseAqualityBmaintenanceEnables coding agents to compact conversation contexts verbatim, make fast decisions through choice, boolean, and rubric scoring, and enforce command safety guardrails.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables host coding agents to conduct evidence-first exploratory testing, adversarial review, reproduction, and resumable reporting through immutable job contracts, action budgets, checkpointed ledgers, integrity-checked artifacts, and optional origin-restricted browser automation.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables monitoring and interruption of autonomous agent runs by detecting infinite tool loops, livelocks, and planning deadlocks, with safety guardrails for prompt injection, spend limits, and sandboxed command execution.MIT
TDQS
Scored across 7 tools
Each tool targets a distinct phase of the task lifecycle: start (begin), run (execute tests), report (finish), checkpoint (resume state), search/remember (read/write memory), guard (test-integrity check). The only mild overlap is start vs checkpoint, since both surface task/budget state, but their descriptions differentiate begin-task from resume-task.
All names are single lowercase words with a consistent terse style (start, run, report, search, remember, guard). The one deviation is checkpoint, a noun rather than a verb, but it still fits the minimal naming convention.
Seven tools is well-scoped for a coding-task harness: three cover the task flow (start/run/report), two cover memory, and two cover resumption and test integrity. Each tool earns its place with no redundancy.
The surface covers the full task lifecycle plus memory and integrity checks, which is strong. Minor gaps exist around memory management (no listing/deleting or verifying lessons) and checkpoint has no explicit restore counterpart, but agents can work around these.