Take over a terminal session without forking
SHORT ANSWER
Open the terminal session in CC Pocket and tap Continue here. It resumes in place when the terminal is idle; it forks only while the terminal is still writing, which prevents two writers from corrupting one transcript.
Observe first
Terminal-owned sessions appear in the project’s session list. Opening one starts in read-only observation, so CC Pocket can stream its output without becoming a second writer.
Continue from CC Pocket
- 1
Wait for the terminal turn to settle
If the terminal is still actively writing, let it finish unless you intentionally want a safe fork.
- 2
Tap Continue here
CC Pocket resumes the same session in place when it is safe to do so.
- 3
Keep working
Prompts, approvals, interrupts, and live output now behave like any other CC Pocket-controlled session.