Known Limitations

This page tracks known limitations in the current Orbital build so users can understand what is captured, what is not captured yet, and when a local rebuild may be required.

Multiple Branches in the Same Chat

Orbital does not yet support multiple branches within the same chat.

When a chat platform creates alternate branches, such as after a user prompt edit or an assistant reply regeneration request, Orbital currently includes only the currently selected branch in the Thread Library and analytics.

This means:

• Earlier or alternate branches in the same chat are not represented as separate branch histories.
• Thread Library rows reflect the branch that was selected when Orbital captured or rebuilt the thread.
• Metrics, Turn View, exports, and related analytics are based on the selected branch only.

Switching Branches

If you switch to a different branch in the chat platform, Orbital currently requires a thread rebuild to sync that branch locally.

After rebuilding, the newly selected branch becomes the local version used by the Thread Library and analytics.

Planned Direction

Branch-aware capture is a planned capability. The goal is to preserve alternate branch histories explicitly so Orbital can distinguish between:

• the original conversation path,
• edited-prompt branches,
• regenerated-assistant branches,
• and the currently selected branch.

Until branch-aware capture is available, treat each rebuilt thread as the selected-branch view of that chat.