Document BrowserCode vs OpenCode differences and resume session issues

[DiazOlveraCo]

Summary

This issue tracks the key differences between BrowserCode (bcode) and OpenCode, and documents specific bugs related to session resumption.

Key Differences (Known)

Feature	BrowserCode (bcode)	OpenCode
Zen API	Not available	Available
Session Resume ID Format	Expected: bcode_...	Shows: opencode_...
Browser Integration	Native via CDP/browser_execute	Not native

Reported Bugs

1. Zen API Unavailable

• Expected: Zen API should work in BrowserCode
• Actual: Cannot use zen API on bcode browsercode
• Impact: Limits AI model options for users

2. Session Resume ID Mismatch

• Expected: Exit should show bcode_<session-id> resume ID
• Actual: Shows opencode_<session-id> (inherited from OpenCode fork)
• Result: Using the displayed ID fails with "invalid session ID"
• Workaround: User must manually replace opencode with bcode in the ID

3. Resume Session Failure

• Error: "invalid session ID" when using the displayed opencode-format ID
• Root Cause: Session storage/lookup uses bcode prefix but CLI displays opencode prefix

Proposed Fixes

1. Update session ID generation to use bcode_ prefix consistently
2. Update CLI display to show correct bcode_ resume ID on exit
3. Add Zen API support or document why it's not available
4. Add migration guide for OpenCode users switching to BrowserCode

Next Steps

• Fix session ID prefix in CLI output
• Fix session lookup to accept both prefixes during transition
• Document Zen API status
• Create comparison docs in README or separate file

[SyedFahad7]

Hi! I'd like to take this. Happy to start with a short BrowserCode vs OpenCode comparison in the docs, and fix the session resume ID so the CLI shows bcode_… (and accepts the displayed ID). Could you assign me if that sounds good?

cc @MagMueller @gregpr07