← The work

Slack integration Beta

Techbase Bridge

Continue a local Codex conversation from a Slack thread.

An illustrative conversation

Keep the conversation going from Slack.

When I’m away from the development window, I still want to ask a question and pick up the same thread. Bridge passes that conversation to the configured local workspace.

  1. You

    Can you check how the import validates missing fields?

  2. Codex via Bridge

    Should I just explain the validation, or also prepare a change?

  3. You

    Just explain it for now.

  4. Codex via Bridge

    The required fields are checked before the import is saved. I can point you to the relevant code next.

Illustrative wording, not a captured session. In interactive mode, questions and approval requests return to the same Slack thread; Bridge never answers approvals itself.

One message, a particular workspace.

The operator configures the working directory and Codex preset before anyone sends a request. A Slack message supplies the question; it does not choose a new executable or working directory.

Keep the context together

Follow-up messages in the same admitted Slack thread use its saved Codex session. A new thread starts a separate conversation, while requests are serialized through the configured workspace.

A question and an approval are different.

In the example, Codex asks what work you want. In interactive mode, the runtime can also ask permission to perform an action. Bridge relays that prompt, and the requester or a configured operator answers it in the same thread. Bridge makes neither decision for them.

When you need to interrupt.

status
Check active or queued work and any pending prompt before deciding whether another request is needed.
cancel
Ask the active turn to stop. Stopping a turn does not reverse file changes or external actions already performed.

“The reply did not arrive” needs care.

A Slack send can fail after an action has already happened. Bridge records uncertain delivery and does not automatically replay potentially executed work after a restart. I would check status and the affected result before deliberately asking again.

Read the conversation and interruption examples ↗

What I want the boundary to make clear.

Bridge makes an existing runtime reachable from Slack. The useful question is who should be able to use that runtime and which permissions it has. An allowlisted Slack user still reaches the configured Codex environment; Bridge is not a new isolation layer.

Attachments are another concrete limit: accompanying text is forwarded, while the file contents are not. If the task needs the file, the conversation has to establish an appropriate way to access it.

A thread connected to your local workspace.

Bridge is for people who already run Codex locally and want to reach that setup through a trusted Slack workspace. It sends messages to one configured local workspace.

The operator chooses the Slack workspace, channels, permitted people and Codex preset. Each admitted thread keeps its own saved session.

Interactive mode relays approval requests and questions to Slack, where the requester or a configured operator can answer. Bridge never approves them automatically. You can also check status or cancel a turn from the thread.

Choose who can use your runtime.

Bridge uses the configured Codex authentication and permissions, so access belongs only with people you trust to use that runtime. It adds no separate sandbox, hosted account service or development coordinator.

The public beta supports Codex CLI, with interactive and noninteractive transports. Text accompanying attachments is forwarded; file contents are not. The repository explains setup, permissions and operating limits.

Ask me about Techbase Bridge →