{
  "id": 19749658,
  "title": "Why does osFoundry make Codex CLI poll the cursor for every resource instead of pushing changes?",
  "url": "https://urgent.news/2026/11/13/osfoundry-codex-cli-changes-push-resource-cursor-poll",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-13T03:20:15.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/bbt-hi/osfoundry-codex-cli-ko-changes-push-krne-ke-bjaay-hr-resource-kaa-cursor-poll-kyon-krvaataa-hai-5064"
  },
  "original_language": "hi",
  "account": "osFoundry's MCP server was tested with a client, revealing limited functionality. The server provides minimal information, and most push channels are closed. A read-only tool, `poll_resource_events`, is available, allowing clients to resume from an event sequence for granted channels. The client uses a sequence cursor, tracking integers for each resource, to poll the server. Rate-limit headers indicate 2000 requests per 61 seconds. The client discovers pollable resources through `list_granted_resources` and `list_project_resources` calls.",
  "summary": "If a client wants to know if anything has changed, the osFoundry's MCP server just gives it that. It was run from the same Mac, without a token: $ uv run --with tiktoken --with jsonschema python3 watch_sim.py == Part 1: live wire, 8 calls each, ms == initialize HTTP 200 median 414.7 p90 757.8 tools/list HTTP 200 median 606.8 p90 716.7 resources/subscribe HTTP 200 median 450.6 p90 550.2 GET (stream) HTTP…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}