Harbor OpenCode implementation does not consider sub-agents. The RFC for v1.7 just added support for them
Our implementation pins to the first sessionId and only keeps track of that trajectory. The latest RFC concluded that sessionId should not be a resolution mechanism, as different sub-agents may share it.
We should move to v1.7 with trajectoryId
Harbor OpenCode implementation does not consider sub-agents. The RFC for v1.7 just added support for them
Our implementation pins to the first
sessionIdand only keeps track of that trajectory. The latest RFC concluded thatsessionIdshould not be a resolution mechanism, as different sub-agents may share it.We should move to v1.7 with
trajectoryId