Jcode integration proposal

[factnest365-ops]

Hey @ogulcancelik, I built a Jcode integration for Herdr — adds herdr integration install jcode support so Herdr can track Jcode agent sessions alongside Pi, Claude, etc.
Already got a working implementation on my fork: https://github.com/factnest365-ops/herdr/tree/master
Would love to get your thoughts before opening a PR. Happy to adjust anything to match Herdr’s direction.

[1jehuang]

I maintain Jcode and would like to take this integration through the current Herdr patterns. Jcode now forwards the HERDR_* pane context, opens headed sessions in Herdr panes, exposes session lifecycle hooks, and resumes with jcode --resume <id>.

My proposed first scope is deliberately narrow: native jcode process detection with screen-manifest state, plus a session-identity hook using pane.report_agent_session and herdr:jcode. I would keep lifecycle state screen-driven rather than claiming hook authority. If that direction is accepted, I can open a tested PR covering install/uninstall, restore mapping, detection, and draft docs.

[ogulcancelik]

hey, that sounds pretty good! as full hook authority is tricky, if you can open a pr with good screen-manifest coverage that would be awesome, please feel free to send pr!