Skip to content

Use Tedix in ChatGPT, Codex and Claude

Add Tedix to Claude, Claude Code, Codex or the ChatGPT desktop app, sign in to your organization, and ask for your first Work in five minutes.

Agent setup

You already talk to an AI assistant every day. This tutorial adds your Tedix organization to that assistant, so it can find your team’s Work, ask a tedi for help, and save a result where your colleagues can see it. It takes about five minutes and needs no terminal unless you use Claude Code or Codex.

Installing the plugin gives your assistant a connection, not power. It cannot change or run anything in your organization until you sign in and choose what it may do, and even then every action follows your organization’s policy.

Before you start

You need:

  • Tedix Cloud beta access: membership in an organization. Tedix Cloud is an invited beta; to request access, use the contact page;
  • a browser in which you can sign in and approve the requested access; and
  • one of the hosts below.

Never paste a token or password into a chat. Sign-in always happens in your browser. The connection address below is the same for every host; you only need to copy it for Claude chat and Cowork:

https://connect.mcp.tedix.dev/mcp

1. Pick your host

Claude chat and Cowork

Open Claude’s settings, go to Connectors, add a custom connector named Tedix, and paste the address above. This gives Claude the Tedix tools; the bundled skills are not included. Cowork runs in its own environment, so it cannot reach anything on your laptop, such as a local Tedix.

Expected result: Tedix appears in Claude’s list of connectors and offers to sign in.

Claude Code

In a terminal, run:

claude plugin marketplace add tedix-hq/tedix-plugins
claude plugin install tedix@tedix-plugins --scope user

Then, inside Claude Code, open /mcp, select the Tedix server, and sign in. Use a current Claude Code release (2.1.274 or later); older versions cannot talk to the Tedix gateway.

Expected result: /mcp shows the Tedix server as connected.

Codex and the ChatGPT desktop app

In a terminal, run:

codex features enable mcp_2026_07_28
codex plugin marketplace add tedix-hq/tedix-plugins
codex plugin add tedix@tedix-plugins
codex mcp login tedix

The first command turns on the MCP protocol version Tedix requires; restart Codex after it. The last one opens your browser to sign in. In the ChatGPT desktop app, no terminal is needed: open the Plugins Directory, enable tedix, and start a new Work chat.

Expected result: in Codex, codex mcp list shows tedix; in the ChatGPT desktop app, a new Work chat offers the Tedix plugin.

ChatGPT on the web

Not supported yet. The Tedix plugin is not in the ChatGPT plugin directory, and a developer-mode custom connector is not a tested path. Use the ChatGPT desktop app or Codex instead.

2. Sign in and choose your organization

When the host asks you to sign in, a browser window opens. Sign in to Tedix, pick the organization you want to use, and review the consent screen. It starts with read access selected; add more only if you need it. You can reconnect later to change this.

Expected result: the browser confirms the connection and you return to the host. Nothing has been changed in your organization.

3. Say hello

In a new chat, type:

Connect my Tedix account

Expected result: the assistant names your account and the organization it connected, and makes one small read to prove the connection works.

Then try one of these:

  • “Find the Work relevant to this task in my organization.”
  • “Ask a tedi to help with this task.”
  • “Save this result as an Output in this Tedix Workspace.”

Expected result: the assistant finds Work, hands the task to a tedi and shows the run’s progress, or saves a result that your colleagues can open in Tedix OS. If it needs an organization or destination you did not name, it asks.

Optional: local hooks with the CLI

If you already use the Tedix CLI, tedix setup agents installs the same plugin into Claude Code and Codex and adds opt-in local hooks that bring your repository’s Tedix context into each session. Every hook stays silent until you turn it on; the CLI guide lists each one. The CLI login and the host’s Tedix sign-in are separate; signing in to one does not sign you in to the other.

If it does not work

Start with the symptom you see.

The assistant does not know Tedix

The plugin is not enabled in this chat. Turn it on in the app you are using, then start a new chat; an open chat does not pick up a new plugin. In Claude chat and Cowork, check that the Tedix connector is added and turned on.

Not logged in or an authorization error

The app has no Tedix sign-in yet. Repeat the sign-in for the app you are using: the connector’s sign-in in Claude, /mcp in Claude Code, or codex mcp login tedix in Codex. Signing in to the CLI does not help here.

Your organization is missing in the browser

Cloud access and organization membership are separate. Ask the person who invited you to confirm your membership. If you have no Cloud access yet, request it through the contact page and wait for beta admission. No one can fix this by sending you a token.

Reference

Navigation

Type to search…

↑↓ navigate↵ selectEsc close