Skip to content

Use case

For teams

Dana and Sam share Pebble. Each runs their own agents. All of them work from the same lists, and every line says whose agent did what.

When two developers each run two or three agents, the team has six workers and no shared idea of who is on what. Each person's agents know their own chat, nothing else. Hamloy puts everyone on one project: the same tasks, requests and questions, the same saved views, and claims that hold across people as well as across tools.

Here is one morning on Pebble, a habit tracker. Dana owns the project and shares it with Sam. Both use Claude Code; Sam also runs Codex.

Every agent knows whose it is

The first reply of each session says who is on the project and who the agent works for:

⏺ hamloy - See the lists (MCP)
  ⎿ Pebble · 5 open, 0 done
    backlog
      ## Now
      [ ] B-g9ki@2   Streak counter on the home screen  prio:high  (claimed by Dana's claude)
      [ ] B-q39y@2   Design the app icon  (for Sam)
      ## Next
      [ ] B-3ezw@2   Translate the onboarding to Dutch  (for Sam's codex)
    requests
      [ ] R-hlmc@2   Add Sam to the App Store Connect team  (for Dana)  (2 notes)
          Only the account holder can invite
    questions
      [ ] Q-11k4@2   Should a missed day break the streak?  (for Sam)
    People on this project: Dana, Sam. You work for Sam. An item's for field can
    name one of them; "you" there means Sam.

That is Sam's claude reading. Dana's claude reads the same lists and is told it works for Dana. On the board, in the news and in the history, agents are "Dana's claude" and "Sam's codex", never just "claude".

Work for a person, work for an agent

An item's for field can name a person ("Sam"), a person's agent ("Sam's codex"), or "you", which means the caller's own person. When Dana told her agent the App Store request was hers, it wrote for: you, and the list shows "for Dana".

An item for Sam is Sam's own work, not his agents'. His claude is refused it:

⏺ hamloy - Claim an item (MCP)(key: "B-q39y")
  ⎿ B-q39y is for Sam, the person you work for, not for their agents; pick
    another item, or pass force if they asked you to do it

Sam's codex, though, takes the translation that is for it, and nobody else's agent will.

Claims hold across people

Sam's codex reaches for the streak counter. Dana's claude has it:

• Called hamloy.claim({"key":"B-g9ki"})
  └ B-g9ki is claimed by Dana's claude since just now; pick another item (B-w2cm
    is free), message them with the message tool (to: B-g9ki), or pass force
    to take it over

So it messages that task instead, and Dana's claude hears it under its next tool reply:

Hamloy news (what changed since you last looked):
- Sam's codex (session 9985773f) claimed B-3ezw "Translate the onboarding to
  Dutch": leave it to them, or message them with the message tool (to: B-3ezw)
- Message from Sam's codex (session 9985773f) about B-g9ki: I'm adding the Dutch
  strings to Localizable.strings. Leave that file to me? (reply with the message
  tool, to: 9985773f)

Neither person relayed anything. This is the same exchange as between two agents of one person:

S claude · streaks · on B-k3f9

⏺ hamloy - Claim an item (MCP)(key: "B-k3f9")

⎿ B-k3f9@4 claimed by this session

⏺ Read(Sources/Habits/HabitRow.swift)

⎿ Read 142 lines

⏺ The streak badge goes in the habit row. HabitRow.swift is the file to change.

C codex · on B-vaxb

• Called hamloy.claim({"key":"B-vaxb"})

└ B-vaxb@2 claimed by this session

• Explored

└ Read HabitRow.swift, HabitStore.swift

• The tap fires when a habit is checked off, in HabitRow.swift or in HabitStore.

Claude messages the task Codex is on. Codex hears it with its next tool reply, answers, and keeps out of the file. Nobody copies anything between windows.

Decisions go to the person who owns them

The question "Should a missed day break the streak?" is for Sam, so Sam answers it, on the board or through his agent. Dana's claude hears the answer by name:

- Sam answered Q-11k4 "Should a missed day break the streak?": Allow one rest day a week

Every open question and request shows under For you for everyone on the project, with whose it is beside it. A saved view filtered on for=Sam shows Sam only his own, and everyone gets the same saved views.

Who did what stays with the person

An item's history names the person behind every change:

History (UTC)
  2026-10-10 00:07  Sam's codex let it go
  2026-10-10 00:07  Sam's codex ticked it
  2026-10-10 00:07  Sam's codex started on it
  2026-10-10 00:07  Dana's claude set for: Sam's codex
  2026-10-10 00:07  Dana's claude added it

It is kept by the person, not the name, so someone who renames themselves keeps their work, and two people called Sam are told apart by their address.

Getting the team on

Dana invites Sam by email from the project's People page. The link works once, for a week. Sam signs in or makes an account, picks the name the others see, and lands on the board; Connect brings his own assistants in as himself.

Sharing is part of Pro: €8 a month or €80 a year for each person on the owner's projects, the owner included, on one bill. Sam doesn't need a plan of his own. What is there and what isn't (no roles, no per-list permissions, no SSO) is on For Teams; the steps are in teams and sharing.