Skip to content
AI assistantsTjati CLI

Use Tjati from your terminal.

Use Tjati from the terminal and from scripts. Sign in once in your browser, then read your day, search your work and capture what comes up.

Connect Tjati CLI

Choose your assistant

How to connect Tjati CLI to Tjati

The Tjati command line, for people, scripts and agents. Signing in happens in your browser, and nothing is typed into the terminal.

Install and sign in
npm install --global @tjati/cli
tjati auth login
tjati today --human
Setup instructions
  1. Install the CLI. It needs Node 24.22 or newer. The package is not published yet, so this command does not work today.
  2. Run tjati auth login. Your browser opens the Tjati sign-in page at auth.tjati.com. Add --no-browser to print the address instead.
  3. Sign in with the email address of your Tjati account. Tjati emails you a 6-digit code that works for 5 minutes. The page can also offer Continue with Apple or Google.
  4. The consent page shows Tjati CLI as a verified app that reaches the Tjati tools and the Tjati API. Choose the permissions and Allow access.
  5. Run tjati auth status --human, then tjati today --human. The CLI keeps the login in your computer’s credential store, or in a file only you can read.

Tjati builds this client. The package is not published to npm yet, so the install line shows what it will be. End-to-end compatibility remains a publish gate.

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

What you are allowing

What Tjati CLI can and can’t do.

You choose the permissions on the consent page at auth.tjati.com. These lines assume you leave the preselected ones ticked.

It can

  • Read your tasks, notes, projects, goals, habits and reminders, and the files attached to tasks and notes.
  • Save a new note or task, and a checkpoint of what it did.
  • Suggest changes for you to approve in Tjati.
  • Edit tasks and notes directly, but only if you leave Update your work ticked.
  • Read your calendar, but only if you tick Read your calendar.
  • Reach the Tjati API as well as the MCP tools. The consent page says so before you allow it.

It can’t

  • Send email or change your calendar. Tjati has no tool for either.
  • Read or draft your mail. Gmail is deferred, so the mail tools return an unavailable result.
  • Attach files to a task or note. That stays something you do in the app.
  • Give itself more permission. Only you can, in the app.
  • Read your past conversations. Tjati sees only what the assistant sends it.
  • Keep working after you sign out or disconnect. Its next request is refused.

Disconnect Tjati CLI any time

In the Tjati app, open Settings → Connected agents, choose Tjati CLI, and choose Disconnect. Tjati refuses Tjati CLI’s next request, then deletes its consent and tokens. You can connect again from Tjati CLI at any time. On the computer itself, tjati auth logout does the same and removes the stored login.

On a server with no browser

Create an API key in the Tjati app (Settings → Connected agents, then Create API key). It is shown once. Keep it in a secret manager, and pipe it in so it never appears in your shell history or the process list. A key you import this way is bound to the gateway it was imported for.

Import a key
printenv TJATI_TOKEN | tjati auth:token-stdin

Try it with Tjati CLI

Your plan, one command away.

Commands to try after you sign in. Your granted permissions decide what each one can do.

  1. 01

    See your day

    Start from what is on your plate rather than a blank prompt.

    tjati today --human

  2. 02

    Search your work

    Find tasks and notes, one result per line, ready for a script.

    tjati search-state "launch plan" --all --ndjson

  3. 03

    Preview a capture

    Without --commit this only previews the task. Nothing is saved until you add --commit and an entity type.

    tjati capture "Review launch plan tomorrow" --json

Before you connect

Tjati CLI + Tjati, explained.

How does tjati auth login sign me in?
It opens your browser at auth.tjati.com and runs a standard OAuth sign-in with PKCE, using a short-lived callback on your own computer. You sign in with an email code and choose the permissions on the consent page.
Where does the CLI keep my login?
In your computer’s credential store: the macOS Keychain, or the Linux Secret Service. Where there is none, such as a headless Linux host, it uses a file only you can read, and it prints that path once.
How do I sign out?
Run tjati auth logout. It revokes the login at the server and deletes it from this computer. You can also choose Disconnect in the Tjati app.
Can the CLI act as an MCP server?
Yes. tjati mcp:serve is a stdio bridge to the remote server, and it uses the same login. Prefer the remote connection in a client that supports it.
Is the CLI on npm?
Not yet. It has not been published, so the install command on this page does not work today.

If something goes wrong

Troubleshooting Tjati CLI.

The command says authentication is required.
The CLI exits with code 3 when it is not signed in. Run tjati auth login again.
My browser did not open.
Run tjati auth login --no-browser. The CLI prints the sign-in address for you to open yourself.
npm cannot find @tjati/cli.
The package is not published yet. This is expected until it is.
It says “Sign up in the Tjati app first”.
There is no Tjati account for that email address. Create your account in the Tjati app, then connect again. Connecting never creates an account.
It says “We couldn’t verify this email address”.
Check that the email address on your Tjati account is verified in the Tjati app, then try again.
The code did not arrive, or did not work.
A code works for 5 minutes, and three wrong tries end it. Ask for a new code. If Tjati says you asked for too many, wait a while first.
The sign-in page asks me to sign in again.
A sign-in older than ten minutes is checked again before Allow access counts. Sign in once more and choose Allow access.
The tools are listed but they say a permission is missing.
That connection was not given the permission. Open Settings → Connected agents, choose the connection, and switch on what it may do.
It stopped working and asks me to sign in again.
The connection was disconnected, or it expired. Connect again from the client. A disconnected connection is never restored by calling again.

Connecting an assistant gives it only what you allow. Read the privacy policy and the terms of service. Questions go to support.

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