Letta + Codex Orchestrator Debugger

Fix Letta server 500 errors by loading OPENAI_API_KEY from ~/planner/.env.

Updated Sep 22, 2025

Search Tags:#codex #debug #environment #orchestrator #let ta

Ready to run

npx skills add https://github.com/EGAdams/planner --skill letta-codex-orchestrator-debugger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Letta + Codex Orchestrator Debugger
Source: https://github.com/EGAdams/planner/tree/main/.claude/skills/letta-codex-debug
Command: npx skills add https://github.com/EGAdams/planner --skill letta-codex-orchestrator-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides practical guidance and tooling to debug and run the hybrid Letta + Codex orchestrator integration, ensuring environment variables are correctly loaded and the orchestration flow behaves as expected.

Core Features & Use Cases

Environment Awareness: Ensures OPENAI_API_KEY and related env vars are loaded before starting.
Orchestrator Debugging: Step through the Letta-Codex integration and identify misconfigurations.
Nuclear Sharing: Guidance for restarting services and validating outcomes.

Quick Start

Run the provided debugger workflow to validate your Letta + Codex orchestrator setup, starting from env loading to script execution.

Frequently Asked Questions about Letta + Codex Orchestrator Debugger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix Letta server 500 errors when creating agents?▼

Letta server 500 errors during agent creation typically occur when the OPENAI_API_KEY environment variable isn't loaded. Source your ~/planner/.env file in restart_letta_server.sh using `set -a` to export variables before starting the server, ensuring credentials are available to the agent initialization process.

How do I debug a Letta and Codex orchestrator integration?▼

Debug Letta-Codex orchestration by validating environment variable loading, verifying script execution flow, and checking for misconfigurations in the orchestrator workflow. Start by sourcing the .env file, confirming API keys are exported, and stepping through the orchestration sequence to identify where the integration breaks.

What environment variables do I need for Letta agent orchestration?▼

At minimum, set OPENAI_API_KEY for Letta agent creation. Load these variables from ~/planner/.env using `set -a` in your restart script to ensure they're available throughout the orchestration process and prevent initialization failures across development and deployment environments.

Can I use Letta with Codex in a hybrid orchestration workflow?▼

Yes, Letta works with Codex in hybrid orchestration. Ensure environment variables are properly sourced before agent creation, adjust timeouts for long-running tasks, and validate the orchestration flow end-to-end to handle both development and deployment contexts reliably.

Why does my orchestrator fail during Letta agent creation?▼

Orchestrator failures during Letta agent creation usually stem from missing or unloaded environment variables, particularly OPENAI_API_KEY. Verify your restart script sources the .env file with `set -a`, check that timeouts accommodate initialization delays, and confirm the orchestration sequence completes each step before moving forward.