I used ghostty for the shell in my agent-manager tool (think something like https://air.dev/ https://air.dev/ but in SwiftUI. One architectural detail i'm still

I used ghostty for the shell in my agent-manager tool (think something like https://air.dev/ https://air.dev/ but in SwiftUI. One architectural detail i'm still going back and forth on is: who should own the PTY? If embedded Ghostty owns it, now i have to have some kind of workaround to instrument what's happening inside the terminal - signals, stdout/stderr events, return code etc. If my parent agent-manager app owns it, now i don't have the nice clean small interface to ghostty (i'm a fan of John Ousterhout style narrow but deep interfaces, pulling complexity down rather than pushing up to parent). Not sure if any other ghostty embedders might have advice. It's on my todo list to task a an agent to "gh repo clone" a few ghostty using shells and report on their arch.