Enterprise AI collaboration system

Codex Feishu Bridge

Connects Codex to an enterprise Feishu workspace. Members can submit questions, files, and long-running tasks from a computer or phone, then add context, check status, and receive deliverables after leaving their desks while an online company workstation continues the execution.

Deployable system | collaborative Codex access in Feishu

Employees repeatedly move requests, files, and results between Feishu and separate AI tools. Complex work is often delegated to a few Codex users, and tasks become difficult to continue once people leave the company workstation
Members submit requests and attachments from Feishu on a computer or phone. The system hands the work to Codex on an online company workstation, accepts follow-up input from authorized members in the same topic, and returns results and files there
Customers receive an enterprise AI work entry point deployed on their own workstation. After going home or leaving their desks, members can continue tasks from their phones, while the team can turn repeatedly proven workflows into reusable Skills so later work follows the same method without depending on a few experienced employees

The project has a deployable Windows 10/11 x64 release. The customer workstation must have Codex installed and signed in; while the workstation and bridge service remain online, members can submit tasks, continue same-topic collaboration, check status, and receive results from Feishu on a computer or phone.

Previous workflow

Employees discussed work in Feishu, then handed requests and files to a few colleagues who knew how to operate Codex.
The operator moved context between chat, the working directory, and the AI tool, then returned responses and files to the group.
After leaving the company workstation, members found it difficult to start or follow up on Codex tasks, while answers and revisions could become separated from tasks waiting for clarification.

What the system takes over

Validate group and member authorization, then decide whether the request can be answered directly or needs a trackable formal task.
A formal task freezes the message, attachments, and topic relationship before Codex runs it in the customer-designated workspace on the company workstation.
The system tracks acceptance, queueing, execution, clarification, and delivery states, then returns text, attachments, or Feishu cloud links to the original topic.
The team can review task processes that repeatedly work and package stable steps, tool choices, and acceptance requirements into reusable Skills for other members to invoke.

What remains human

When key input is missing, Codex asks in the original topic and continues only after an authorized member provides an unambiguous answer.
Members check whether the final response and attachments are complete and usable, then decide whether to revise, cancel, or start a new topic.
Deployment, real external sending, and paid generation remain separately authorized actions and are not triggered automatically by ordinary chat.
A new Skill requires team confirmation of its conditions, execution steps, and acceptance criteria before it is used for later tasks.

Delivered outputs

A direct answer in the original Feishu topic or a trackable asynchronous task with its own identifier
Text, images, Office files, videos, and other task artifacts generated or revised by Codex
Queryable records for accepted, running, waiting-for-input, completed, failed, or uncertain task states
Reusable Skills derived from repeatedly effective work processes so other members can complete similar tasks with the same method

Usage scope

The system depends on the customer's own Feishu application permissions and signed-in Codex environment and is not open to unauthorized groups or members.
Mobile Feishu is the remote task entry point, while processing still happens on the company workstation; tasks cannot continue when the workstation is powered off or the bridge service is offline.
The system does not learn from employee behavior without confirmation. Only effective workflows reviewed and approved by the team are packaged as new Skills.
The system handles access, task orchestration, and result delivery; it does not replace human confirmation of final content, files, or external actions.

Your business does not need to copy this project; diagnosis starts from the actual workflow.

Discuss your workflow