## additional features for capsule

### agent_id parameter is REQUIRED
capsule exists wholly to enable the spacetime messaging infrastructure. as such, it cannot launch without being provided an agent_id

### terminal tab rename
before invoking psmux, output the necessary OSC/`[Console]::Title = "{agent_id}"` to rename the terminal window/tab appropriately

### stdout message to indicate what's happening
historical message for the user to see after exiting the session. should come after launching the detached psmux, and waits for the cc session_id to be populated onto the perch before firing:
i.e. ```
Now launching a spacetime capsule for agent 'doyle'...
a: {cc_session_id}
``` --> (no perch and/or not live)
or ```
Reactivating the spacetime capsule for agent 'doyle'...
a:{cc_session_id}
``` --> (live + already has perch)
+ if live, on another newline add `p:{psyche_session_id}`
where 'a' represents the agent's cc session, and p represents the psyche's cc session.
---> finally, the attached psmux call follows.

### --resume flag uses the passed agent_id ONLY. can't accept a raw claude code session id
the latest session ID should be stored against the agent_id in .registry or else somewhere in the perch -- this might already be happening. this session ID is then used to populate the `--resume <session id>` flag passed to claude when invoking via psmux.


## capsule: default psmux stylings
try to get it functioning more like powershell (hilight sticks instead of insta-copy), and looking cleaner. no gaudy green bg on the status bar. ideally these psmux settings augmentations are stored within the project folder. if psmux can be guided to a settings file with a flag, then use that so the settings augmentations can be kept somewhere out of the way i.e. in `.claude/`.