congrats on the public launch! it's been clear to me for a while now that agents will need their own ways to communicate and an asynchronous inbox/task system is a necessity already. will point my agents at the repo to see how we can leverage
Thanks! I was pleasantly surprised with how naturally a lot of email idioms seemed to align here. In retrospect, it makes sense if you think of human-to-agent communication as another form of asynchronous communication.
Why does it have to be a desktop app vs a self hostable web app?
That way it can truly run asynchronously, even with the computer switched off.
congrats on the public launch! it's been clear to me for a while now that agents will need their own ways to communicate and an asynchronous inbox/task system is a necessity already. will point my agents at the repo to see how we can leverage
Thanks! I was pleasantly surprised with how naturally a lot of email idioms seemed to align here. In retrospect, it makes sense if you think of human-to-agent communication as another form of asynchronous communication.
I have a more basic question; I am trying to understand its purpose.
How does this compare with connecting your agent to your ticket tracker, e.g., https://linear.app/build ?
If it is about local work, how does it compare with simply having your agent monitor a directory for ticket files?