{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreif4w37j3fhtyjor44we6vxzpm4apecrnryvc7lzqtorocmk6pxwta",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mhgiktml6n62"
  },
  "path": "/t/the-fastest-way-to-feed-ghc-type-errors-to-llm/13827#post_8",
  "publishedAt": "2026-03-19T12:58:18.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "turion:\n\n> Apologies, Github Copilot does connect to HLS automatically (it just sometimes needs to be reminded of this fact), so it receives the type errors immediately. This is the fastest way I know so far.\n\nCorrect, if you have hls running in VSCode, you just need to give the agent the permission to read the problems panel (which is not enabled by default I believe) and it’s able to take the errors appearing there into account. This is great if you have hls + vscode setup. I was looking for something more lighweight which I can run on demand without having to run some persistent process in the background and manage its state.",
  "title": "The fastest way to feed ghc type errors to LLM"
}