What We Shipped: Geta.Team v2.1.1 — OpenAI Codex Integration, 13 Skill Fixes, and Smarter Defaults
Version 2.1.1 adds a third AI engine to the platform. OpenAI Codex, powered by GPT-5.4, now sits alongside Claude and OpenCode as a fully integrated CLI provider. This release also includes connectivity fixes across 13 skills, environment cleanup, and a default behavior change for new employees.
OpenAI Codex: A Third Brain for Your AI Employees
Every AI employee on Geta.Team can now run on OpenAI Codex. The integration covers the full lifecycle: authentication, session management, task execution, and resume support.
Authentication uses the same device code flow pattern established with Claude. Admins initiate the process from Settings, approve through OpenAI's portal, and the credential is shared across all employees automatically.
Session isolation keeps each employee's work separate. While authentication credentials are shared at the container level, every employee maintains their own session directory, preventing cross-contamination of context and history.
AGENTS.md auto-generation handles a key compatibility detail. Codex reads AGENTS.md rather than CLAUDE.md for its system instructions. The platform now generates AGENTS.md automatically from each employee's existing CLAUDE.md, so switching between providers requires zero manual configuration.
Tool mapping bridges a fundamental architecture difference. Where Claude exposes discrete tools (Bash, Read, Grep, Glob, Edit, Write), Codex routes everything through a single exec_command tool. The platform translates between the two, mapping each Codex command to the appropriate tool type based on content analysis.
Resume support works identically to Claude sessions. Users can pick up interrupted Codex conversations with /resume UUID, maintaining full context continuity.
The provider selector in chat now shows three options, with Codex appearing in green alongside Claude's orange and OpenCode's purple.
Skill Connectivity Fix Across 13 Integrations
A reliability issue affected how skills communicated with the backend inside employee containers. Environment variables for the internal API host and port were intermittently unavailable, causing skills to fail silently or throw connection errors.
The fix hardcodes the internal network address directly into all 13 affected enterprise skills: Delegate, Discord, Google Calendar, Google Drive, Google Gmail, Office 365 Calendar, Office 365 Drive, Office 365 Mail, Office 365 SharePoint, Slack, Teams, Telegram, and WhatsApp. This eliminates the dependency on environment variable propagation and makes skill connectivity deterministic.
Cleaner Container Logs
All VibeCoder container spawns now include DOTENV_CONFIG_QUIET=true, suppressing verbose dotenv initialization warnings from container output. Logs are easier to read and debug without the noise.
New Employees Are Now Isolated by Default
Previously, new employees joined with team collaboration enabled, meaning they could see colleagues and receive delegated tasks immediately. Starting with v2.1.1, new employees are isolated by default. This gives users explicit control over which employees participate in team workflows, rather than requiring them to opt out individually.
Existing employees are unaffected by this change.
Skills Preserved on Restart
Employee skill customizations, including any custom skills created during conversations, now survive container restarts. The platform no longer re-syncs skills on startup, preventing overwrites of modifications employees have made to their toolsets.
