AI agents

Agents with Tidigar Business

Tidigar Business · Paid

Let your own AI agent read and change the plans your organisation keeps in Tidigar Business or on your Tidigar Server. The agent works on a whole plan at a time, and what it saves appears in Tidigar, also for anyone who has the plan open.

Try the launch planning exercise if you want a concrete task before connecting. This guide covers connection setup and the rules for saving shared plans.

Try a small change first

Choose a disposable plan in the organisation you intend to connect. Keep it open in Tidigar.
Connect using one of the setups below. Ask the assistant to read the plan and report its title, dates and organisation before changing anything. A read-only connection is enough for this check.
With write access, ask it to change one activity and save in the same plan, preserving the other work. Ask for a summary and the shared plan link.
Check the saved result in Tidigar. Disconnect or revoke the token when the trial is over.

The CLI and MCP operate on the same stored plans; installing both does not create a second library. A shared plan link opens the stored plan for its members. Ask explicitly for a copy when you want a separate share link instead.

What an agent can do

With a token, or connected as a chat assistant, an agent can, in one organisation:

list its plans,
read a plan,
create a plan,
change a plan and save it,
delete a plan, after asking you, and restore it,
make screens of a plan's saved views, write the stories they play, and give you their links, such as your status slides played as one plan.

A deleted plan stays in the trash for 30 days. Deletion checks the version the agent read: if someone saved since, nothing is deleted. The agent cannot manage members, billing or tokens, or reach another organisation. See saving and access below for revision checks and merge choices.

A screen shows one saved view to anyone with its link, without an account. The agent asks before making one and gives its link only to you. Owners can turn off Let agents make screens to prevent agents making screens and retrieving their links; agents can still change screen names and stories. End a screen separately when its public link should stop working.

For a plan kept only in your browser, files or calendars, follow the copy-based planning exercise. This connection reaches stored Business or Server plans.

A chat assistant

For ChatGPT, Claude.ai and other chat assistants that add apps or connectors by address. You need no token: you approve the assistant in Tidigar, and the assistant's service keeps the access out of the chat.

In the assistant's settings, add a custom connector (in ChatGPT, an app in developer mode) with the address https://app.tidigar.com/mcp. For Tidigar Server, use your server's address followed by /mcp.
The assistant opens Tidigar. Sign in if asked.
Check that the assistant's name and the address it returns to are the ones you just added, choose the organisation and Read only or Read and write, and choose Allow.

Each connection reaches one organisation. To connect another, add the connector again. If you connected for reading and ask the assistant to save, it reports insufficient_scope; connect again with Read and write.

If the assistant supports starting a connection during the conversation, it can open that setup flow. Otherwise add the connection in its settings, then return to the original task. The host handles OAuth and keeps credentials outside the chat. Instructions or an installed skill do not grant access by themselves.

If the assistant cannot add a connector, it cannot edit the stored original. A separate share-link copy is an option only if you ask for one; it does not save your change to the stored plan. Never paste a token into a chat.

The agent's stored-plan guide covers checking the connection, finding the original, validating, saving and handling conflicts. After connecting, the agent checks the organisation and write access and continues the task.

Create a token for a coding agent

Personal tokens are for a computer, coding environment or script configured outside the chat. Chat assistants use the delegated OAuth connection above.

Open Tidigar Business and choose Account → Agent access → New token.
Name it after the agent or computer that will use it, such as “Claude Code on my laptop”.
Choose Read only, or Read and write if the agent should save plans.
Choose the shortest expiry that fits the work, at most 365 days.
Copy the token. It is shown only once.

Make one token for each agent or computer, so you can stop one without stopping the others. A token never gives more access than you have: if you can only view an organisation's plans, its agent can only read them too.

Keep the token secret

A token works like a password to your organisation's plans.

Never paste it into a chat, a prompt, a document, a repository or a command line. A chat is stored and can be shared.
If you pasted it somewhere by mistake, revoke it at once and make a new one.
Store it only where the agent uses it without seeing it in the conversation, as in the setups below.

Set up a coding agent

An agent on your computer

For agents that run commands on your computer, such as Claude Code, Codex CLI or Cursor. You need Node.js 20 or later.

Install the tidigar command. On a Mac or Linux:

curl -fsSL https://tidigar.com/agents/install-cli | bash

On Windows, in PowerShell:

irm https://tidigar.com/agents/install-cli.ps1 | iex

Run the same line again later to update. Then sign in, and paste the token when it asks. The token is not shown as you paste, and it is kept in your computer's keychain or credential manager.

tidigar login

For your own Tidigar Server, add its address: tidigar login --server https://your-server. Check that it works:

tidigar status

Last, give your agent the Tidigar skill (how to install it), or add Tidigar as an MCP server. In Claude Code:

claude mcp add tidigar -- tidigar mcp

Other agents take the same command, tidigar mcp, in their MCP settings. For a read-only token, use tidigar mcp --read-only.

Then ask your agent, for example: “Read our launch plan in Tidigar and move the beta two weeks later.”

A cloud coding agent

For agents that run in someone else's cloud, such as Codex in the cloud, Claude Code on the web or a CI job.

Make a token only for that environment, with the shortest useful expiry.
Add it as the environment variable TIDIGAR_TOKEN in the service's environment settings, never in the task or the prompt. For example, see environments in Claude Code on the web or Codex.
If the service limits network access, allow app.tidigar.com, or your Tidigar Server's address.
Give the agent the Tidigar skill. It uses the token directly, or the tidigar command if the environment's setup installs it with the line above.

Anyone who can run tasks in that environment can use the token. Revoke it when the work is done.

How saving and access work in detail

A whole plan and its revision travel together

The assistant reads the whole project, edits it and saves with the revision it read. The revision check prevents a save based on an old plan from silently replacing newer work. With CLI, tidigar plans update plan.json --merge requests a merge; without --merge, a stale revision is refused. MCP offers the same choice.

If two people change different activities, a merge can keep both. If both rename the same activity differently, the assistant explains that conflict and asks which name to keep. A conflicting merge saves nothing until its choices can be resolved. If the plan changes again while you decide, new conflicts may need answers too.

If the assistant reports write_unknown, the save may have happened even though its answer was lost. Ask it to read the stored plan and compare the result before another write. Repeating the command without checking can repeat an operation you already completed.

Scope, membership and storage all limit access

A connection belongs to one organisation, rather than one selected plan. Choose it carefully: read access can inspect that organisation's accessible plans. Write access also depends on your current membership, subscription and organisation restrictions. A write token cannot turn a viewer into an editor. Owners can turn off Allow agent access (MCP and CLI) separately from restrictions on taking copies. Turning agent access off revokes the organisation's personal tokens and chat connections; turning it back on requires new connections.

The local MCP process uses the CLI's credentials. tidigar mcp --read-only exposes only reading and validation tools even with a write token. Remote chat connections use approval in Tidigar instead of a personal token. Installing the skill gives the agent instructions; it grants no account access by itself.

Local login requires the system credential store. There is no plaintext-file fallback if that store is locked or unavailable. In a hosted environment, TIDIGAR_TOKEN takes precedence over locally stored credentials. Keep it in that environment's secret settings; anyone able to run code there can use it.

Disconnecting ends access, not saved work

Revoking a token or disconnecting an assistant prevents further access, within about a minute in Business. It does not undo saved changes, remove copies the assistant already read, or end screen links it created. Delete a screen separately when you want its public link to stop working.

With TIDIGAR_TOKEN set, tidigar logout revokes that environment token but cannot remove the variable from the service's settings. Remove it there too. Without the variable, logout revokes and removes the local credential. If a network failure prevents revocation, the local credential remains so you can retry; you can also revoke through Agent access.

Check and fix

If something does not work, run:

tidigar doctor

It shows the version, where the token is kept, whether the server answers and whether the token is still valid.

Your agent may report one of these:

Message	What it means
`merge_conflicts`	Someone saved the plan first and changed the same things. The agent asks you which version to keep for each.
`stale_revision`	Someone saved the plan first and the changes could not be combined. The agent reads it again and redoes its change.
`read_only_token`	The token can only read. Make a token with Read and write to let the agent save.
`subscription_required`	The organisation is not paid: its trial or subscription has ended. The agent can neither read nor save its plans until an owner subscribes; the connection then works again.
`agent_screens_off`	The organisation's owners let only people make screens and copy their links.
`write_unknown`	The save may have succeeded. Read the plan and compare it before writing again.
`invalid_token`	The token is wrong, expired or revoked. Make a new one and sign in again.
`insufficient_scope`	The chat assistant was connected only for reading. Connect it again with Read and write.

Stop access

On a computer, run tidigar logout. It revokes the token and removes it from the computer.
Anywhere, open Account → Agent access in Tidigar Business and revoke the token. Every agent using it loses access within a minute.
For a chat assistant, open Account → Agent access and choose Disconnect under Connected assistants. It loses access within a minute.

For developers

Scripts and tools can call the same operations over HTTPS. See the public API.