What does my team see when I share a project?

Its status, its links, the projects inside it, its boards and the notes from calls about it. Your screen, your other projects, your to-do list and your agents’ own notes stay yours.

Can two people’s AI agents update the same project?

Yes. When a teammate’s agent reports what it finished on a shared project, the report goes onto that project, and its status is rewritten with it, saying whose update each part came from.

Can a ticket have more than one person on it?

Yes. A person field holds as many people as you like, and a board can have several, like Owner and Reviewers. Everyone on a ticket hears about changes to it in their inbox.

Is this only for engineering teams?

No. A project can be a campaign, an account, a client, a hire or a codebase, and boards start from templates for marketing plans, content calendars, sales pipelines, hiring and launches as well as sprints.

Does it replace Linear or Jira?

For a small team, it can: boards with short ticket ids, several people per ticket, sub-tickets, cycles, blocked-by links, an inbox, views and GitHub pull requests moving tickets. Their CSV exports import with the ticket keys kept: how to move over.

How teammates work on the same project in Cachejay

One project, everyone on it

Cachejay keeps a page for each of your projects, current through the day from your screen, your calls and your AI agents. On a team, you can share a project, and everything inside it, with one click or one sentence to your AI app. From then on it's the team's project:

Everyone sees it beside their own projects, on the web and in their AI apps.
Everyone updates it. When your teammate's Claude Code or ChatGPT reports what it finished, the report goes onto the shared project, and its status is rewritten with it.
Everyone keeps its links: the brief, the repository, the design file, the CRM view.
Its boards are the team's, so anyone can take a ticket, move it or comment on it.

› where does the spring campaign stand?
  ⎿ cachejay · projects_now
Spring campaign (Jo's, shared with Acme), updated 20 minutes ago:
· Launch email approved by legal, scheduled for Tuesday (Oct 21, Sam)
· Paid social budget agreed on the agency call (Oct 20, call)
Next: the webinar landing page (Oct 21, Jo)

Links: Brief, Figma file, Analytics dashboard
Board: Spring plan, 3 of 8 done

Tickets with more than one person

Work on a shared project lives on boards, and each card is a ticket with a short id like SP-12. Say “SP-12” in Slack, in a pull request or to your AI app and it's clear which one you mean.

A ticket can have as many people on it as the work needs: an owner and a reviewer, two writers, the account executive and the solutions engineer. A board can have several person fields, and each holds several people. A team board can be open to the whole team, or kept to the people working on it.

Boards start from templates, and most of them aren't for engineers: a marketing plan, a content calendar, a launch checklist, a sales pipeline, hiring. Each has the fields that kind of work needs, and you add your own.

Hearing about changes

Everyone on a ticket hears when it changes: whoever made it, the people on it, anyone who commented and anyone @mentioned. It lands in their inbox on the boards page, unread until they open it, with a few quick changes to one ticket kept to one line. Changes an AI app makes count too, shown as “Sam via ChatGPT”, and your own AI app can read your inbox for you: “what changed on my tickets today?”

Four teams

Made-up examples, one per kind of work.

A marketing team's launch

Jo shares the spring campaign; the landing page and the email sequence inside it are shared with it. Sam writes the emails and Kim runs paid social. Each asks their own AI app what's left and gets the same status, written from all three people's updates. The launch email ticket has Sam as owner and Jo as reviewer, so when legal's changes come back, both of them hear.

A sales team's accounts

Each account is a project with its call notes, shared with the team. The deal ticket on the sales pipeline has the account executive and the solutions engineer on it. Before the renewal call, either of them asks “what did Northwind ask for last time, and what did we promise?” and gets the answer with the call's date.

A design studio's client

The client is the project. The design file, the feedback doc and the brand folder are its links. Two designers share the rebrand tickets; the client calls say which round of feedback is current, which is the hardest thing to work out from the files alone.

Engineers on one feature

The project's status already lists the open pull request and the failing test, because each engineer's agent sessions and reports feed it. With GitHub connected, a branch named alex/web-14-signup links its pull request to WEB-14, and merging it moves the ticket to Done.

When someone is away

Because everyone is already on the project, a vacation stops being a handoff. Whoever covers sees the same status, links and tickets, puts their name on the tickets they take, and leaves comments that wait in the inbox of the person who's away. The checklist for the day before you go is in how to hand off your work before a vacation, and the other side is how to pick up a teammate's project.

What stays private

Sharing is per project and off until you turn it on. Your teammates see what's listed above for the projects you share, and nothing else: not your screen, not your other projects, not your to-do list, not what your AI agents keep for themselves. Stop sharing and its notes leave the team.

Starting

Start a team on cachejay.com, share a project from its page (or ask your AI app to share it), and add its links. Teams are $18 a seat a month. Cachejay for Teams, or try Cachejay on your own first, 14 days free with no card.