Running several projects

Running three or five things at once is where “I’ll remember” stops working. It’s also where tuckit asks a question it doesn’t ask a single-project user: is this all one board, or several?

There’s no setting for it. It follows from two facts, so those come first.

The two facts that decide it

Card numbers count per org. The 42 in ACME-42 counts inside one org and nowhere else. Two orgs both have a 42, and they’re unrelated cards with different prefixes.

One agent connection reaches exactly one org. When your agent connects, the browser asks which organisation the connection is for, and what it gets back works only for that one. An agent connected to your blog’s board can’t see your SaaS board, and can’t accidentally file something into it.

Everything below follows from those two.

Shape A: one org, an area per project

Your acme org holds areas called blog, saas, client-work.

• One board, one Inbox. Everything from every project lands in the same place and you sort it in one pass.
• One connection. Set it up once and every folder uses it.
• One run of numbers. ACME-1 through ACME-400, across everything.
• Cards move between projects in a click, because moving between areas is free.

This is right when the projects share a what should I do next question, when you genuinely sit down and pick the most important thing across all of them. Side projects for one business usually work like this.

It goes wrong when they don’t. Five unrelated projects on one board means the board can’t answer “what’s next” until you filter it, and a board you filter before reading is data, not a surface.

Shape B: one org per project

acme-blog, acme-saas, bigco-contract, each its own org.

• Boards stay readable. Each answers “what’s next” on its own.
• The numbers read like the project. BLOG-7 and SAAS-7 are obviously different things, which matters when you paste one into a chat.
• Separate Inboxes, so nothing lands in the wrong project.
• One connection per project, which is the cost. See below.
• No cross-project view. There’s no page showing all your boards at once.

This is right when the projects have different clients, different timelines, or would never compete for the same afternoon.

Choosing

Ask which sentence you say more often:

• “What should I work on today?” → Shape A. You want one ranked surface.
• “What’s the state of the blog?” → Shape B. You think per project, and mixing them is noise.

If you’re unsure, start with Shape A. It’s the cheaper mistake: splitting later means making an org and re-creating a handful of cards, whereas merging later means reconciling two runs of numbers that already appear in old chat logs.

Adding a second org

Settings → Account → Organisations → New organisation. Pick a name and a short lowercase one for the address, and tuckit derives the card-number prefix from it. That’s the BLOG in BLOG-7. Your account can hold as many as you like, and the sidebar switcher moves between them.

Cards don’t move across orgs. If you split a board later, re-create the cards you still care about and leave the rest.

Pointing each repository at the right board

With Shape A there’s nothing to do. One connection, installed once, works everywhere.

With Shape B, each folder needs its own connection. The pattern is one server entry per board, named after the board and scoped to the folder, so opening an agent in that folder reaches that board and no other. In Claude Code, run this inside the folder:

claude mcp add --transport http tuckit-blog https://app.tuckit.dev/mcp --scope project

--scope project writes it into that folder’s .claude/settings.json, so the server exists only there. On first use the browser opens and you choose the acme-blog organisation. Repeat per folder with a distinct name: tuckit-saas, tuckit-bigco.

Verify this one on your own machine

This pattern assumes your agent stores a separate credential for each server name, even though every name points at the same address. That’s the agent’s behaviour, not tuckit’s, and we haven’t confirmed it across versions. Check before you trust it: connect the second board, then ask each agent What's the state of this project? from its own folder. If both answer with the same org, they’re sharing one credential. Use a separately authorised client, or a static token per org from Settings → Agent, until they don’t.

If you use the plugin rather than a hand-added server, it installs one named tuckit. Add the extra per-folder ones by hand as above.

Two habits that only matter at this scale

Write things down anywhere, sort them in one pass. With several boards you’ll want to file everything perfectly the moment you notice it. Don’t. That’s the tax that makes you stop noticing. Leave things in the Inbox with no area and clear them in one sitting. Writing down without sorting is a proper path precisely so noticing stays cheap.

Write back when you switch, not before you sleep. With one project you can reconstruct yesterday from memory. With five you can’t, and the moment you lose is the context switch, not the end of the day. Before you close a project, leave the note and tick the steps. With the plugin installed, “reconcile the board” does it for you. The daily loop is the full version.

Where to go

• The daily loop: the day-to-day.
• What’s on the screen: what an org, area and card are.
• Connect your agent: the other AIs, and connecting by hand.