OpenAI · ChatGPT · Open Source

Bifrost Turns Feishu Into a Remote Console for OpenAI Codex

By Bifrost · Aug 12, 2026

Read original on juejin.cn ↗ Google Translate ↗ Alt translation

Remote agent access that preserves the full local toolchain closes the gap between "I'll deal with it when I'm at my desk" and immediate action. For teams already running Codex or Claude Code on always-on machines, a chat-based control plane means alerts, ideas, and long-running jobs don't stall on physical presence.

Summary

Bifrost bridges Feishu and a locally running Codex CLI agent so that a developer can dispatch real engineering work from a chat app. A message in a private or group chat reaches Codex through Bifrost's session manager, which maintains independent working directories, task queues, and context per conversation. Codex reads the local repo, runs tests, and uses the machine's full toolchain; Bifrost streams plans, tool calls, and stage results back as Feishu cards.

Setup keeps the machine running Bifrost and Codex powered on and online, then binds a Feishu provider with a single CLI command. Once connected, slash commands let you inspect and switch the working directory, check runner status, and stop execution. Group chats isolate projects by binding different repos, and the bot only acts on explicit @-mentions or slash commands, not casual discussion.

Scheduled tasks add a cron layer on top: a daily CI summary, a pre-release check, or a dependency audit can fire on a timer and land in a designated Feishu chat. The security model pushes for restricted permissions, repo-scoped sessions, environment-variable secrets, and mandatory human confirmation on high-risk actions.

Takeaways

— Bifrost sits between Feishu and a local Codex runner, maintaining per-conversation sessions, working directories, and task queues.

— The machine running Bifrost and Codex must stay powered on and awake; it is not cloud-hosted execution.

— Binding Feishu takes one CLI command with an interactive OAuth flow, or environment variables for an existing app's credentials.

— Slash commands inside Feishu let you check status, switch the repo working directory, view queues, and stop execution.

— Group chats isolate projects: each group gets its own session key, context, runner, and working directory, and the bot only acts on explicit @-mentions or commands.

— Scheduled tasks use cron expressions to trigger agent prompts on a timer, with results delivered back to a specified Feishu chat.

— Security recommendations include default restricted permissions, repo-scoped sessions, env-var secrets, human confirmation for high-risk actions, and read-only diagnosis before modification.

Conclusions

Bifrost treats the chat app as a thin control surface rather than a development environment, so Codex still operates on the real local repo with the full toolchain — no stripped-down sandbox.

The design choice to make group-chat messages passive by default (only explicit commands wake the agent) solves the noise problem that plagues bot-in-channel setups.

Scheduled prompts turn the same agent infrastructure into a cron-driven operator, which is a small conceptual leap with outsized utility for on-call and maintenance workflows.

Concepts & terms

Bifrost IM Gateway

An open-source bridge that connects instant-messaging platforms (starting with Feishu) to local AI coding agents like OpenAI Codex, managing sessions, working directories, task queues, and progress reporting.

Codex Runner

The local execution environment for OpenAI's Codex CLI agent, which reads repositories, runs shell commands, edits files, and executes tests on the host machine.

Feishu Provider

A configured Feishu bot integration in Bifrost that authenticates via OAuth or app credentials and routes messages to a specific Codex runner.

Source: juejin.cn ↗ Google Translate ↗ Backup ↗