Feature: Each pet follows its own Claude Code session

[quocdaijr]

What do you want?

Hi, I saw the README mentions routing agents/projects to their own pet window — does this already work for multiple parallel Claude Code sessions running at the same time?

If not, it'd be great to have each concurrent session automatically get its own dedicated pet.

Motivation

I often run multiple Claude Code sessions in parallel. It would be great if each pet could follow one specific session, so I can tell sessions apart at a glance.

Proposed behavior

• Each session gets its own dedicated pet
• The pet stays attached to that session throughout its lifetime
• Running N parallel sessions → N different pets visible

Why

Makes it much easier to manage parallel sessions visually.

Thanks for the amazing work on OpenPets — really love the project! 🐾

[alvinunreal]

Thanks for calling this out. Short answer: not automatically today.

What works now is per configured pet/project routing: when a Claude/OpenPets integration is configured with --pet <petId>, events acquire a short-lived desktop lease and show that selected pet in an explicit agent pet window. So different projects can be configured to different pets.

What does not exist yet is automatic per-concurrent-Claude-session assignment. The current Claude hook path is effectively keyed by the configured pet id, not by a Claude session id, and agent pet windows are reused per pet id. That means two parallel Claude sessions using the same configured pet will share the same pet window rather than getting two separate pets.

I agree the behavior you proposed is the right direction: detect a stable Claude session identity, assign an available/dedicated pet for that session, keep that mapping alive for the session lifetime, and clean it up when the session stops/expires. I'll keep this issue open for that work.