Daeda AI is not tied to a single chat surface. If you already live in Codex, Claude Code, Cursor, or any terminal-based AI agent, that is where the work happens - no separate window to learn, no context to duplicate.

Describe the workflow you need in the terminal and Daeda AI drafts the full plan against your live portal: triggers, branches, actions, the properties they depend on. The plan is readable in the terminal before anything touches HubSpot. You refine it in the same thread, submit it as a Write Plan, then approve it inside Daeda AI in HubSpot before the workflow lands in your portal.

So engineers and power-user RevOps who already build with AI in the terminal can treat HubSpot like any other system they drive from the command line. The plan still routes through the same Human-Approved review and the same Write Plan record it would from the chat app, it just starts in Codex instead of a chat window.