trying something tonight to save $: hooking up the conductor cloud mcp to cursor! my orchestrator has to be a cursor cloud agent since i want zero risk of it dying overnight due to usage limits. but i'll save a ton of money if the agents it spins up use my subs via conductor :) i didn't want to sacrifice quality though, so i also made a pstack 'adapter' for conductor. it teaches agents how to use pstack outside of cursor. so e.g. /poteto-mode still works. besides cost savings, the nice thing is that my cursor cloud agent can route to my codex or ant subscription based on usage. and that even if my subs run out, the cursor agent can technically complete the job itself. not sure if this will work but it'd save thousands of dollars for long runs!