Griptape Prompt Driver: Griptape Cloud

This is the driver the pack's own team would love you to use: GPT-4o served through Griptape Cloud, the hosted side of the griptape.ai platform this whole pack comes from. It's the "house model" - one model, one choice, no dropdown to agonize over. You're effectively renting a managed OpenAI brain that's already wired into Griptape's ecosystem, and it pairs naturally with Griptape Cloud's other hosted services, like their knowledge-base and vector-store clients.

Honest framing: for most people this is a middleman you don't strictly need. If you have a plain OpenAI key, the OpenAI-compatible driver gets you GPT-4o directly and probably cheaper. Griptape Cloud earns its keep when you're leaning on the rest of the platform - hosted RAG, managed tools, not running infrastructure yourself. Use this driver because you're in the Griptape Cloud world, not because it's the best model deal.

How it works

The node builds a Griptape GriptapeCloudPromptDriver authenticated with a GT_CLOUD_API_KEY, pointed at GPT-4o. Your agent's prompts go to Griptape Cloud, which handles the OpenAI call on their side, and the reply comes back as usual. Output is a single DRIVER (PROMPT_DRIVER) for agent and RAG wiring.

The inputs that matter

• model - a single-option dropdown (gpt-4o). Not configurable beyond that; if you want other models you're in the wrong driver.
• api_key_env_var - env-var name, default GT_CLOUD_API_KEY. Get the key from cloud.griptape.ai/configuration/api-keys.
• response_format - default or json_object. Pick json_object when the agent's output feeds downstream parsing.
• max_tokens, temperature, seed, min_p, use_native_tools, max_attempts_on_fail - the standard kit.

Installing it

Pack install: ComfyUI Manager → Griptape → ComfyUI-Griptape, restart, or

cd ComfyUI/custom_nodes
git clone https://github.com/griptape-ai/ComfyUI-Griptape

Set GT_CLOUD_API_KEY in Settings → Griptape or your environment.

Common issues

The env-var-name trap applies here like everywhere: type GT_CLOUD_API_KEY, not your key. The bigger consideration is billing - Griptape Cloud is a paid platform, and a chatty agent can rack up tokens without any visible warning until the invoice lands. If you're on the free/trial tier, watch rate limits; they'll show up as throttling errors mid-workflow.

Pack-wide gotchas also apply: griptape[all] can stomp ComfyUI's torch on Nvidia (reinstall with the cu121 wheels), and if you hit ImportError: cannot import name '...' from 'griptape.drivers', your griptape library is out of date - python -m pip install griptape -U and restart.