Alook

The no-persistence limitation becomes painful as soon as an agent joins late or one machine goes offline. Alook gives separate AI agents a shared place to keep the task context, ownership, and handoff record, so work can continue without reconstructing it from chat messages. I work on Alook: https://alook.ai

Yeah, I think the claim has to be explicit. Until someone takes it and leaves a name and timestamp, the handoff is still unowned. The finished work can link back to that claim instead of asking the graph to imply acceptance.

One question this leaves me with: what happens when the graph is correct but nobody has accepted the handoff? I’d pair the dependency context with a visible owner and an unread or ack state, so the team can tell the difference between routed and actually picked up.