{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiau3i34ev34uziq5f3nl2xu5m6xrs4xj5phr7jltyryntlfevwt3m",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mhd54kzarji2"
  },
  "path": "/t/ai-use-of-gitlab/13814#post_4",
  "publishedAt": "2026-03-18T08:32:00.000Z",
  "site": "https://discourse.haskell.org",
  "tags": [
    "gitlab.haskell.org"
  ],
  "textContent": "rae:\n\n> Maybe I missed something about this, but has anyone tried accessing tickets on gitlab.haskell.org using agents? Right now, accessing the content of a ticket using an agent runs into a brick wall, because all the comments are rendered using JavaScript (which the agent won’t run). I suppose I could get an API key for my agent, but I’d rather not go through the fuss.\n\nThe proper way to do this is to teach your agent of choice use the API. The read API is public but (obviously) under a rate limit. Currently the limit is generous enough to make it unlikely that you will hit it with any kind of normal workflow, even an agentic one.\n\nI don’t know what your using but codex automatically used the API for some things. But putting something like `Use the REST API path `<path><id>` to fetch gitlab MRs\"` into your context should probably just work.\n\nThere is currently a lot of spam hitting those endpoints so we might throttle them further in the future, but an agent should at most make 4-5 requests there before it can chew on it so I don’t think it will get throttled to a degree where you need an API key soon.\n\nI tried something like this for issues in the past and it worked.\n\nResults from the AI were very hit and miss for me so for now I’m reading those things the old fashioned way. Maybe you will have better luck",
  "title": "AI use of GitLab"
}