{
  "id": "page:docs-harness-features-backlog-gaps-tools-capabilities-gap-tools-012",
  "_kind": "Page",
  "_file": "wiki/docs/harness-features-backlog/gaps/tools-capabilities/gap-tools-012.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/harness-features-backlog/gaps/tools-capabilities/GAP-TOOLS-012.md",
    "sourceKind": "repo-docs",
    "title": "GAP-TOOLS-012: Language Server Protocol Integration for Code-Aware Routing",
    "displayName": "GAP-TOOLS-012: Language Server Protocol Integration for Code-Aware Routing",
    "slug": "docs/harness-features-backlog/gaps/tools-capabilities/gap-tools-012",
    "articlePath": "wiki/docs/harness-features-backlog/gaps/tools-capabilities/GAP-TOOLS-012.md",
    "article": "\n# GAP-TOOLS-012: Language Server Protocol Integration for Code-Aware Routing\n\n| Field | Value |\n|-------|-------|\n| Category | tools-capabilities |\n| Priority | High |\n| Effort | L |\n| Status | Missing |\n\n## Description\nIntegrate Language Server Protocol (LSP) awareness into the orchestrator's task routing and code analysis capabilities. When process definitions involve code modifications, the orchestrator should be able to query LSP servers for type information, references, diagnostics, and completions to make smarter routing decisions and validate task results.\n\n## Current State\nCode-aware tasks are delegated to harnesses blindly. The orchestrator has no understanding of the codebase's type system, symbol references, or diagnostic state. Task validation relies entirely on the delegated harness reporting success/failure. No LSP client exists in the SDK.\n\n## Target State\nAn optional LSP client module that the orchestrator can use to: query symbol definitions and references before delegating refactoring tasks, validate that delegated code changes produce no new diagnostics, provide type context to task prompts for code-aware harnesses, and support go-to-definition routing for cross-package tasks in the monorepo.\n\n## Dependencies\n- [GAP-ROUTE-001](../effect-routing/GAP-ROUTE-001.md) -- smart routing engine for code-context-enriched routing\n- [GAP-PROC-004](../process-composition/GAP-PROC-004.md) -- parameter schemas for typed code task inputs\n\n## Key Files\n| Component | Path |\n|-----------|------|\n| Harness adapters | `packages/sdk/src/harness/` |\n| Task definitions | `packages/sdk/src/tasks/` |\n| Agentic tools | `packages/sdk/src/harness/agenticTools.ts` |\n\n## Recommendation\nPhase 3-4 implementation. Start with a lightweight LSP client that can query diagnostics and symbol info. Use diagnostics as a post-task validation step. Enrich task prompts with type context for code-modification tasks.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-harness-features-backlog",
      "to": "page:docs-harness-features-backlog-gaps-tools-capabilities-gap-tools-012",
      "kind": "contains_page"
    }
  ]
}