Codex in your terminal. With your permission.

Connect Codex

Termilino connects the desktop Codex client to a local MCP bridge. The integration does not require an agent on your server. OpenAI provides Codex separately; Termilino is developed by PWODEV.

1. Install Termilino in Applications. Open Settings > Codex and choose Connect Codex.
2. For first setup, reconnect MCP or restart Codex so it discovers the tools. If you move the app later, reconnect the integration.
3. Connect to your server in Termilino. Right-click its tab, open Codex and choose viewing or control. Copy the connection prompt into the Codex chat that will work with this tab.

One terminal, visible work

Codex submits commands into the same interactive terminal you see. Your current directory, shell environment and remote-user permissions apply. The input and resulting terminal output appear in Termilino; command acceptance alone does not mean it completed successfully.

SSH credentials are handled by Termilino. The MCP interface does not return stored SSH passwords, private keys or key-file paths to Codex. Shared terminal text and permitted server metadata can still be read; avoid printing secrets in a shared terminal.

Viewing, pause, private mode and revoke

Viewing allows reading and blocks agent input. Control allows reading and input. Pause blocks new agent input while reading remains possible. Resume explicitly restores input. Typing or pasting into a controlled terminal pauses agent input before your input is sent.

Private mode blocks both reading and input and clears the captured snapshots for that tab. Revoke removes the live share. Revoke all access in Settings > Codex also clears saved server permissions. Locking the app blocks integration access.

Pause and revoke do not stop a command that already runs remotely. Use the normal terminal controls, such as Ctrl+C when appropriate, or manage that process on the server. Closing SSH is not a guarantee that every remote process stops. Data already read by Codex cannot be recalled.

Server permissions and multiple tabs

Connecting the integration alone grants no server access. You can share only chosen tabs manually, or allow discovery for chosen saved servers and folders. Discovery and permission to connect without asking are separate settings. Keep approval on when you want to decide on each connection.

Settings > Codex lists shared tabs across windows. Select several rows to copy a combined connection prompt; selection itself grants nothing. Shares do not survive app restart or SSH reconnection. Moving a shared tab pauses input; a duplicate starts private. Shares are not authenticated isolation between Codex chats.

Restrict execution to approved commands

In Settings > Codex you can restrict execution to saved commands from approved command folders. This blocks arbitrary command submission, raw terminal input and agent edits to commands. New or changed commands need approval again. Saving or editing library entries otherwise requires a separate permission and never runs them by itself.

This limits actions through Termilino; it is not a sandbox for the remote shell or for other tools available to Codex. A permitted command can call scripts, and server-side permissions still apply.