Hi team, I tried to email you with a privacy question. I used the email address on your Privacy page, but it bounced back as unknown, and there's no other contact address/form on your website. Is there a way to get in touch?
It most likely is. We are using Ubicloud (which seems to work the same way hf jobs does) and it's also down. GitHub is not sending out Webhooks and is also not able to queue external jobs. If we had to emergency deploy anything now I'd have no idea how to really do that...
I am not sure if all Webhooks were affected or only those regarding actions. Theres not much information given besides "Webhook deliveries may be delayed."
The /tree feature is incredible for context management. It's really surprising the other harnesses haven't slurped it up yet. It lets you rewind back to any previous message and fork the conversation from there, removing your 'side quest' (e.g. where you dig into something the agent said) from the context. Some other harnesses have a 'rewind' feature, but this lets you maintain the previous conversation history in a separate thread, and even jump between them.
You can do that in Copilot in VSCode. There’s a fork icon before every message that creates a new session from that point. The relationships are not maintained in a tree though (not sure if Pi does that).
Claude code in the cli also has /fork to clone the current session state. But if you use it more than once or twice that quickly becomes hard to manage. Actual tracking in a tree sounds like an awesome feature (and one that I love in conversational UIs like openwebui as well)
Yes, pi's works a bit better since it exposes the whole tree to you, but in the simple case of forking to a new conversation it is about the same as Cursor and probably other coding agents.
One thing you can do in pi that you can't in Cursor: Have a 5-prompt conversation, jump back to prompt 3 and have a new conversation [call this convo2], then jump back to the original point 5, then jump back to convo2.
So fork is really only needed for when you need to interact with the conversation tree in two separate processes.
For those interested in this I also recommend autobase, a set of ansible roles for a highly available postgres cluster on hetzner or other clouds: https://github.com/autobase-tech/autobase
Just FYI, those discussions might be ending because your analogy comes across as a threat to punch them in the mouth, rather than because it convinces them.
My interpretation of the concern is that propagate implies that the new value is being pushed out to other resolvers, when in fact those other resolvers pull the new value (once their cached value expires).
I started using this today and am really enjoying the notifications when agents are awaiting input, and the status indicators!
But it feels odd to have it outside of tmux. I've got everything else in tmux, but I have to switch to another terminal tab to get to my agents, and then back to my normal shortcuts. I find that a bit jarring... Is that what other folks are doing?
reply