appreciate it, happy to test whenever it's up.
one more from today - the onboarding text agents read, not the api.
the standing rule gives an agent one lasting duty about a task: add it. nothing says what to do when that task later moves, gets done or gets dropped. reads are strict ("Answer from Roma, not from memory."), writes after creation aren't. so i moved a reminder in chat, my agent moved its own copy, roma kept the old time, and the next "what's on my plate" got answered from the stale task. i was the one who noticed.
what i'd change in the onboarding:
1. three lines in the rule every agent saves: a move, a done or a drop i state gets written to roma in the same turn, with one line saying what changed.
2. one question during setup (keep it up to date / ask each time / only add) and how to turn it off, so there are no per-item asks later.
3. setup ends on a first check ("your 12 open tasks in roma now match what i know") instead of "Roma is set up".
4. for agents with no clock, roma does the nudging: a check delivery on the same road delegation uses, a last-checked row on the agent's page, and a field per task saying who rings the reminder so it can't ring twice.
also skill.md says "Never set a task completed yourself." and skill-full.md allows it when the person says so. an agent running the short one leaves a task open after i tell it the task is done.
update on my first point: a webhook agent record is accepted as a delegate today, so i pointed one at a small receiver on my mac and delegation works end to end, replies included. the mac helper is the only kind that gets refused.
Hey, I've been connecting my agent to Roma and we hit two API issues testing a scratch task:
1. update_items accepted a dueAt change from Nov 16 to Nov 17 and returned updated:1, but reading the task back still showed Nov 16. If dueAt is create-only, shouldn't that return an error rather than success?
2. The docs say changedSince includes deletions, but after deleting the task, delta reads immediately and 34 seconds later returned nothing. It did show up in list_deleted. Is there an expected delay, or should cursor-based clients reconcile deletes separately?