Cursor bugs limit Dippy ability to operate effectively

[nickdavies]

While trying to build out #128 and use Dippy at work, I noticed that the hooks system is quite different and broken in Cursor.

Currently only Deny works to prevent commands from running and any other response results in the human getting asked for the preToolHook and with the beforeShellExecution deny works again but then ask or allow both just default to whatever the builtin cursor allowlist says.

I can't seem to find any way to get the tri-state out of cursor currently except if I wrap up Dippy in a command that somehow does it's own approval/denial system out of band of cursor and then only return allow/deny and never ask.

Perhaps the answer here is just a big warning or saying cursor is not supported until the hooks improve but I am interested in your thoughts

[ldayton]

Thanks for digging into this, @nickdavies — your findings match what we're seeing. The core problem is that Cursor's hooks can't express Dippy's three-state decision: only deny takes effect, while ask and allow both fall through to Cursor's own allowlist. Without a real ask, Dippy can't do the thing it exists to do, so there's no way to make it work properly on Cursor right now.

Given that, I'm going to treat Cursor as explicitly unsupported/experimental until its hook system can return the full tri-state, and note that in the docs so nobody expects it to work. I'll keep this issue open as the place to track that — if Cursor's hooks improve, this is where we pick it back up.

I'm parking #128 against the same reasoning (more there).