{"slug": "a-fresh-agent-session-sees-nothing-what-aisync-news-shows-and-what-it-doesn-t", "title": "A fresh agent session sees nothing: what aisync news shows, and what it doesn't", "summary": "The maintainer of aisync, an MIT-licensed local CLI for multi-agent context management across AI coding tools, tested the `aisync news` command in version 0.2.10 and documented that a session's first call only sets a cursor, so events logged before that point are never reported. In a throwaway hub with Claude Code and Codex agents, a second call surfaced two logged events while a third printed \"nothing new,\" and per-session cursors stored under `state/cursors/` kept two Codex sessions isolated. The maintainer said the late-start behavior is by design and that showing the last N events on a first call remains an open question for the project.", "body_md": "aisync is a local CLI for Multi-Agent Context Management, Coordination & Observability across AI coding tools. I maintain it. One of its jobs is telling an agent what the other agents did while it was working, and the command for that is `aisync news`. I ran it with two agents in a throwaway hub to see what it shows, and what it does not.\n\nI used a temporary virtualenv, pointed `AISYNC_HOME` and `HOME` at temp directories so my real hub and tool files were never touched, and installed `aisync-cli` 0.2.10.\n\n```\npython3 -m venv v && ./v/bin/pip install aisync-cli==0.2.10\nexport AISYNC_HOME=\"$PWD/home\" HOME=\"$PWD/fakehome\"\n./v/bin/aisync init\n./v/bin/aisync news --agent codex\ncursor set; next call shows what changed after now\n```\n\nA session's first `news` call only sets a cursor. Anything that happened before that moment is not reported. If you want the earlier history you use `aisync tail` or `aisync status`.\n\nClaude Code logs two events, then Codex asks again:\n\n```\n./v/bin/aisync log --agent claude-code --project demo --kind dev_log --summary \"added retry to the uploader\"\n./v/bin/aisync log --agent claude-code --project demo --kind blocked --summary \"waiting for API key\"\n./v/bin/aisync news --agent codex\n[aisync] While you were working, other AI tools changed things:\n- 06:04 claude-code dev_log @ demo: added retry to the uploader\n- 06:04 claude-code blocked @ demo: waiting for API key\nIf any of this touches files you are editing, coordinate (`aisync claims`) before going on.\n```\n\nA third call prints `nothing new`: the cursor moved past those two events.\n\nClaude Code had already run `aisync news --agent claude-code` once, so its cursor was set (the output was the same \"cursor set\" line). It then logged a `decision` event and ran `aisync news --agent claude-code` again. The output was `nothing new`. Without that first call the second one would only have set the cursor, so the order matters. The result matches the intent (\"what other tools did\"), and it means `news` is not a general activity feed.\n\nWith `--session`, two Codex sessions keep separate cursors. Session `s1` set its cursor, Claude Code logged a note, and then session `s2` set its cursor. Asking `s1` showed the note. Asking `s2` printed `nothing new`, because its cursor was set after the note. The cursors are small files, one per agent and session, under `state/cursors/` in the hub (for example `codex-s1.json`).\n\n`news` automatically for Claude Code, Codex and Cursor were not part of this test. I called the command by hand.\nA session that starts late misses the history by design. Whether that should be an option (for example showing the last N events on the first call) is a question for the project, and I have not changed it.\n\nRepo (MIT): [https://github.com/MaxonT/aisync](https://github.com/MaxonT/aisync)\n\nSite: [https://maxont.github.io/aisync/](https://maxont.github.io/aisync/)\n\nInstall: `pip install aisync-cli`\n\nThis post and the test run were written and tested by an AI agent (Claude Code) for the maintainer. The outputs above are copied from that run.", "url": "https://wpnews.pro/news/a-fresh-agent-session-sees-nothing-what-aisync-news-shows-and-what-it-doesn-t", "canonical_source": "https://dev.to/maxont/a-fresh-agent-session-sees-nothing-what-aisync-news-shows-and-what-it-doesnt-59n5", "published_at": "2026-11-16 12:07:19+00:00", "updated_at": "2026-11-16 12:21:30.540613+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "developer-tools", "mlops"], "entities": ["aisync", "Claude Code", "Codex", "Cursor", "MaxonT"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/a-fresh-agent-session-sees-nothing-what-aisync-news-shows-and-what-it-doesn-t", "markdown": "https://wpnews.pro/news/a-fresh-agent-session-sees-nothing-what-aisync-news-shows-and-what-it-doesn-t.md", "text": "https://wpnews.pro/news/a-fresh-agent-session-sees-nothing-what-aisync-news-shows-and-what-it-doesn-t.txt", "jsonld": "https://wpnews.pro/news/a-fresh-agent-session-sees-nothing-what-aisync-news-shows-and-what-it-doesn-t.jsonld"}}