Conversation
…rowser Replaces the top-tab Chat/Browser split with a single screen: WebView fills the whole viewport, and the chat lives in a @gorhom/bottom-sheet on top with snap points at 12% (input bar peeks above the browser) and 92% (chat history scrolls above the input, which stays pinned to the sheet's bottom and rides the keyboard via BottomSheetTextInput). Backdrop appears only at the expanded snap point and collapses on tap. Adds @gorhom/bottom-sheet + react-native-gesture-handler. Wraps the root in GestureHandlerRootView. Drops app/(tabs)/ and the TopTabBar component. BlinkingTabIcon.tsx is now orphaned but left in place. Run with: cd mobile2 && npm install && npm start Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 56f87ab03e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| deps: { navigate }, | ||
| onEvent, | ||
| }); | ||
| apiHistory.current = updatedHistory; |
There was a problem hiding this comment.
runAgent always prepends SYSTEM_PROMPT before sending (mobile2/agent/agent.ts), but this caller stores the entire returned transcript back into apiHistory. On the next user message, that stored transcript is passed in as history, so another system message is prepended again, and this repeats every turn. In multi-turn chats this bloats context rapidly and can degrade model behavior because the same system instruction appears many times; store only non-system turns (or strip the leading system message) before reusing history.
Useful? React with 👍 / 👎.
| if (!el || !el.tagName) return; | ||
|
|
||
| // Skip nodes already emitted in the priority/action prelude. | ||
| if (depth > 0 && opts._skipPrioritySet && opts._skipPrioritySet.has(el)) return; |
There was a problem hiding this comment.
The new priority prelude can collect container elements like role="searchbox" as “text entry surfaces”, then walk skips those nodes entirely in the main traversal. Because the prelude only emits formatLine for the collected node (no descendants), any nested controls under that container (e.g., the actual input/button refs) disappear from both outputs. This causes missing actionable ref_ids on common composite widgets and can block follow-up actions.
Useful? React with 👍 / 👎.
1 participant
No description provided.