Chat with the page
⌘E opens a chat with Claude beside the page you are reading, as in Dia. Claude gets the page’s address, title and text, so you can ask for a summary, an explanation or a translation without copying anything. It runs on Claude Code on your Mac, with your own Claude login (see How OpenArch talks to Claude).
Open the chat
Section titled “Open the chat”Press ⌘E, or choose Ansicht › Mit der Seite chatten (View › Chat with the page). The panel opens to the right of the page, with the cursor in its field.
Before the first message, the panel shows three questions to start with, such as “Fasse die Seite zusammen” (sum up the page); a click sends one. Or type your own: ↩ sends, ⌥↩ starts a new line. While Claude answers, the send button becomes Anhalten (Stop).
In split view, the chat sits to the right of all sides and belongs to the tab you opened it on. There is no page chat in private windows, and in Little OpenArch ⌘E only beeps: move the page into the main window with “In Space öffnen” first.
Ask about a selection
Section titled “Ask about a selection”Select text on the page and press ⌘E, or right-click it and choose Claude fragen (Ask Claude), the first item of the menu. The chat opens with the text above the field, under Auswahl (Selection). It goes along with your next message as the focus of the question; in a new chat, the suggested questions change to “Erkläre die Auswahl” (explain the selection) and “Übersetze die Auswahl ins Deutsche”. The × beside it leaves it out.
With the chat open, select other text and press ⌘E again: that text becomes the focus instead. With nothing new selected, ⌘E closes the chat.
Add other tabs with @
Section titled “Add other tabs with @”Type @ in the field. A list Tab dazunehmen (Add a tab) shows up to eight of the space’s tabs, under the line and pinned, whose title or address contains what you type after the @. ↑ and ↓ move through it, ↩ or Tab picks a tab, Esc closes the list.
A picked tab appears in your text by its name and as a chip above the field; the chip’s × leaves it out again. Its text goes along with the next message, so you can compare several pages or sum them up together. A tab that is asleep or was never opened loads in the background first.
What goes along
Section titled “What goes along”| What | When | Up to |
|---|---|---|
| The page: address, title and text | With the first message, and again once the tab shows a different page | 60,000 characters |
| The selection | With the next message after you chose it | 20,000 characters |
| Each tab named with @ | With the next message | 30,000 characters each |
The text is what the page shows: its article or main area when that holds more than 500 characters, otherwise the text of the whole page. Longer text is cut off at the limit. A page that is still loading is waited for, up to about 15 seconds; if its text cannot be read, Claude is told so. Small chips under each of your messages show what went with it.
OpenArch reads the page through Chrome’s DevTools protocol inside its own tab, not through an open port, so this works without AI control.
Answers and links
Section titled “Answers and links”Answers stream in as they are written and show as Markdown: code in boxes, headings in bold, lists with dots. Links, and addresses written out in the text, open as new tabs next to the page. Claude is asked to answer in the language you write in, to keep it short, and to say so when the answer is not in the page.
If Claude Code is missing on the Mac, the chat says so and how to install it.
Close, come back, start over
Section titled “Close, come back, start over”⌘E, Esc in the chat, or the × in its header (Schließen (⌘E)) closes the panel. The chat keeps its conversation: ⌘E brings it back as it was, and a follow-up question continues the same conversation, so Claude still knows the page and its earlier answers.
The pencil in the header, Neuer Chat zu dieser Seite (New chat about this page), clears the chat and starts a new conversation.
Each tab has its own chat, and it lasts as long as the tab. Closing the tab, or “Heute aufräumen”, ends it. Page chats are never saved, so quitting OpenArch ends them too.
Where it runs
Section titled “Where it runs”Every message is one run of Claude Code in a folder of OpenArch’s own,
~/Library/Application Support/OpenArch/PageChats, away from your files.
Claude Code keeps its usual transcript of these sessions in ~/.claude/projects,
as it does for every session; the Agents view leaves them
out.
Your Claude Code skills and slash commands run in this chat too, from the command bar: see Skills in the command bar.
What Claude gets and what it may do
Section titled “What Claude gets and what it may do”Claude gets the text described above and your message, and nothing else from the browser: no cookies, no screenshots, no other tabs unless you name them with @. OpenArch adds a short note that explains the chat and these parts of the message.
The chat runs with Claude Code’s default permissions. A run cannot stop to ask you, so anything that would need your approval is refused and shows in the chat as “… nicht erlaubt” with a button Erlauben und weiter (Allow and continue), which allows it for this chat. With AI control on, the chat also gets OpenArch’s browser tools; Claude is told to use them only when you ask it to do something in a tab, and the first use needs that same button.
How the runs work in detail: How OpenArch talks to Claude.