Skip to content
AI assistantsCodex

Bring Tjati to Codex.

Bring your Tjati project into Codex before the first change. Give the session the goal, the open work, and a place to leave the follow-ups that matter.

Connect Codex

Choose your assistant

How to connect Codex to Tjati

Connect your Tjati account to Codex. Sign in with OAuth, choose what your assistant can access, and start with a read-only request.

Add and sign in with Codex
codex mcp add tjati --url https://api.tjati.com/mcp
codex mcp login tjati
Setup instructions
  1. Run the add command below in your terminal to register the remote Tjati MCP server.
  2. Run codex mcp login tjati and complete the Tjati sign-in in your browser.
  3. Review the requested scopes, then inspect the connection with codex mcp list.
  4. Start a Codex conversation and ask it to list your Tjati areas before allowing writes.

OpenAI documents remote HTTP MCP and OAuth login in Codex. Tjati end-to-end compatibility remains a publish gate.

Docs-supportedRevoke access in Tjati anytime
One connection. Your Tjati context.https://api.tjati.com/mcp

Try it with Codex

Give the coding task the bigger picture.

Example requests to try after you verify the connection. Your granted scopes determine which tools are available.

  1. 01

    Understand the outcome

    Use the existing plan to establish scope before touching code.

    “Read my Tjati release project and list the open tasks relevant to this repository. Do not change anything yet.”

  2. 02

    Connect the plan

    Keep engineering steps connected to the outcome they support.

    “Break this implementation proposal into Tjati tasks linked to the release goal. Show me the proposal before creating them.”

  3. 03

    Leave a clear handoff

    Make the next session start from an explicit set of open questions.

    “Capture the unresolved review questions in Tjati and propose which project each belongs to.”

Before you connect

Codex + Tjati, explained.

How do I add Tjati to Codex?
Run codex mcp add tjati --url https://api.tjati.com/mcp, then codex mcp login tjati. Complete OAuth and run codex mcp list to inspect the configuration before testing a read-only tool.
Is this setup for Codex or ChatGPT?
These are Codex CLI MCP commands. Hosted ChatGPT and dots use account plugins and have separate setup paths; they do not read your local Codex configuration.
Does a Codex connection have unrestricted Tjati access?
No. Tjati checks the installation’s granted scopes for each tool. Start with read access and proposals, and grant execution authority only for the work you intend to delegate.

Read this page without this page

A direct lane for agent runtimes.

No visual parsing and no JavaScript required. Start with the concise guide, then load only the contract depth the task needs.

Start small. Go deeper when needed.

  1. Recommended

    The concise first read for connection, authority, safe defaults, and operating rules.

    /agent.mdtext/markdownOpen resource

  2. Discovery

    A low-token map of canonical Tjati resources and their purpose.

    /llms.txttext/plainOpen resource

  3. Complete

    Every client setup, scope, delivery rule, and readiness check in one context file.

    /llms-full.txttext/plainOpen resource