# A fresh agent session sees nothing: what aisync news shows, and what it doesn't

> Source: <https://dev.to/maxont/a-fresh-agent-session-sees-nothing-what-aisync-news-shows-and-what-it-doesnt-59n5>
> Published: 2026-11-16 12:07:19+00:00

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.

I 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.

```
python3 -m venv v && ./v/bin/pip install aisync-cli==0.2.10
export AISYNC_HOME="$PWD/home" HOME="$PWD/fakehome"
./v/bin/aisync init
./v/bin/aisync news --agent codex
cursor set; next call shows what changed after now
```

A 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`.

Claude Code logs two events, then Codex asks again:

```
./v/bin/aisync log --agent claude-code --project demo --kind dev_log --summary "added retry to the uploader"
./v/bin/aisync log --agent claude-code --project demo --kind blocked --summary "waiting for API key"
./v/bin/aisync news --agent codex
[aisync] While you were working, other AI tools changed things:
- 06:04 claude-code dev_log @ demo: added retry to the uploader
- 06:04 claude-code blocked @ demo: waiting for API key
If any of this touches files you are editing, coordinate (`aisync claims`) before going on.
```

A third call prints `nothing new`: the cursor moved past those two events.

Claude 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.

With `--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`).

`news` automatically for Claude Code, Codex and Cursor were not part of this test. I called the command by hand.
A 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.

Repo (MIT): [https://github.com/MaxonT/aisync](https://github.com/MaxonT/aisync)

Site: [https://maxont.github.io/aisync/](https://maxont.github.io/aisync/)

Install: `pip install aisync-cli`

This 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.
