Skip to content
AI assistantsOpenAI Dots

Bring Tjati to OpenAI Dots.

Give your dot a plan to refer back to. Start with access to your Tjati context, then define what it may read, what it should propose, and which decisions stay with you.

Connect OpenAI Dots

Choose your assistant

How to connect OpenAI Dots to Tjati

Dots use the apps and plugins connected to your ChatGPT account. Start by making Tjati available in ChatGPT, then ask your dot to check the connection.

First request for your dot
Check whether my connected Tjati plugin is available to you.
The Tjati MCP endpoint is https://api.tjati.com/mcp.
If it is available, list my areas without changing anything.
If it is not available, tell me what connection step is missing.
Setup instructions
  1. Check that dots and custom MCP plugins are available in your ChatGPT account or workspace.
  2. Where custom MCP servers are available, add Tjati using https://api.tjati.com/mcp and complete OAuth.
  3. Enable the connected Tjati plugin for your dot and review its permissions.
  4. Ask your dot to list your areas. If Tjati is unavailable, stop and use another client; do not assume the connection is supported.

OpenAI documents plugin access for dots. Tjati availability for your dot depends on account and workspace settings; this setup is not yet verified end to end.

Setup to verifyRevoke access in Tjati anytime
One connection. Your Tjati context.https://api.tjati.com/mcp

Try it with OpenAI Dots

Ongoing help starts with clear boundaries.

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

  1. 01

    Verify access first

    Confirm the connection before giving your dot an ongoing responsibility.

    “Check whether my Tjati plugin is available. If it is, list my areas without making any changes.”

  2. 02

    Brief an ongoing goal

    Set a concrete goal and agree on what useful follow-up means.

    “Read my Tjati fitness goal and its linked habits. Summarize the plan and ask what kind of follow-up I want.”

  3. 03

    Bring back a proposal

    Keep an ongoing assignment focused on results you can review.

    “Review the open questions in my Tjati launch project. Bring me a proposed next step and explain what needs my decision.”

Before you connect

OpenAI Dots + Tjati, explained.

How would my dot access Tjati?
Dots use supported plugins connected and enabled for your ChatGPT account. First make Tjati available through an allowed ChatGPT connection, then ask your dot to verify a read-only tool. This Tjati setup is not yet verified end to end.
Will my local Codex MCP settings enable Tjati for dots?
No. A local Codex configuration is separate from ChatGPT plugin access. Do not assume a Tjati server configured in your terminal is automatically available to your dot.
Does this page promise autonomous Tjati changes?
No. Availability and actions depend on the connected plugin, workspace policy, Tjati scopes, and the host’s approval rules. Begin with a read-only check and explicitly review any proposed changes.

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