Bohdan Triapitsyn
a5aa32446d
The preview panel worked by proxying a dev server through OpenChamber's own origin and rewriting the HTML that came back. Anything the rewriter did not anticipate broke, and pages that refuse to be embedded never loaded at all. This deletes the proxy (-1604 lines and its tests) and merges the preview and browser panels into one surface backed by a real Chromium view. What the panel is now - A `<webview>` in its own session partition: logins and cookies persist, hot reload works because nothing is rewritten, DevTools are one click away. - Annotation: pick one element, drag a region, or draw freehand, write a note, and it reaches chat with a screenshot of the visible page with the marks on it. - Toolbar: hard reload, page zoom, device sizes, a light/dark switch that applies to the page rather than the app, and cookie/cache clearing scoped to the panel alone. - Several pages at once, each tab showing the page's own favicon, and an address bar that suggests pages already visited in this project. - Dev servers are listed from what is actually listening on the machine, checked against what a project announced, so a server is offered no matter how it was started. One that is still starting is waited for instead of failing. Remote dev servers The desktop app binds a local port and pipes raw bytes to the OpenChamber host over the existing authenticated connection, so the page keeps its own origin at the root of its own host. The reachable set is exactly what discovery reports and is re-checked per connection, so an authenticated client cannot dial arbitrary local services on the host. Links and redirects to another loopback port stay on the machine that served the page. A tunnel that cannot be opened is reported; it is never replaced by the plain loopback URL, which would answer from the user's own machine under a remote address. Agent control Browser actions are a separate `openchamber_web` tool: open, snapshot, click, type, scroll, inspect computed styles, resize between mobile/tablet/desktop, and capture a screenshot into `.openchamber/screenshots/` in the project. The existing `openchamber` tool keeps sessions, worktrees and scheduled tasks. Each has its own setting in the new Settings -> General -> OpenChamber Tools section, and the plugin is not injected at all when both are off. Capability belongs to the connected client, not to configuration: a client declares on its event stream that it can drive a page, which only a Chromium host does. Exactly one client performs each request — it claims the request before acting, and the first claim wins — because deciding by whose result arrives first would be too late for a click that already happened. No client listening is answered immediately with an explanation rather than a timeout. Runtime boundaries Web tabs get a plain iframe that can display a page but not inspect one. The VS Code extension no longer offers the surface at all, since nothing that makes the panel worth having works there. Mobile is unaffected. Native boundary Camera, microphone, location and device-picker requests from panel pages are denied — Electron grants them by default when no handler is set, and the panel loads whatever address the user types. Page capture, appearance emulation and storage clearing verify that their target belongs to the panel's own session instead of trusting a web-contents id from the renderer. Persisted state Stored `preview` tabs migrate to `browser` (v13 -> v14). Context panel tab limits are now per surface, so filling one surface no longer evicts another's tabs. Address history is stored per project and per runtime. Documentation `preview.mdx` and `desktop-browser.mdx` rewritten across all locales, the agent tool settings path corrected, new `DOCUMENTATION.md` for the browser-control broker and the dev tunnel, and the `ui-api-decoupling` skill updated where it still described the deleted proxy.
41 lines
2.9 KiB
Plaintext
41 lines
2.9 KiB
Plaintext
---
|
|
title: Ferramenta de controle para agentes
|
|
description: Permita que um agente gerencie sessões, worktrees e tarefas agendadas do OpenChamber pelo chat.
|
|
---
|
|
|
|
# Ferramenta de controle para agentes
|
|
|
|
Use a ferramenta de agente `openchamber` para gerenciar o trabalho no aplicativo diretamente pelo chat. Ela vem ativada por padrão quando o OpenChamber executa seu próprio servidor OpenCode local; não é preciso instalar outra ferramenta nem executar um comando de shell.
|
|
|
|
## O que você pode pedir
|
|
|
|
Peça ao agente em linguagem natural. Por exemplo:
|
|
|
|
- “Crie uma nova sessão do OpenChamber neste projeto, use o modelo `openai/gpt-5.6-sol` e envie este prompt: revise o fluxo de autenticação.”
|
|
- “Crie uma nova sessão do OpenChamber para esta tarefa em um worktree separado e peça para ela adicionar testes ao fluxo de login.”
|
|
- “Use o OpenChamber para listar minhas 10 sessões mais recentes e inclua o status atual delas.”
|
|
- “Crie no OpenChamber uma tarefa agendada chamada Revisão dos dias úteis que envie este prompt às 09:00 de cada dia útil: revise as alterações desde a última execução.”
|
|
- “Execute agora a tarefa agendada do OpenChamber chamada Revisão dos dias úteis.”
|
|
- “Verifique a sessão do OpenChamber chamada Revisão de autenticação e mostre a resposta mais recente do assistente.”
|
|
|
|
A ferramenta pode listar projetos e preferências de modelos, criar e continuar sessões, bifurcar uma sessão, criar sessões em worktrees isolados e gerenciar tarefas agendadas. As sessões iniciadas assim aparecem no OpenChamber como qualquer outra, então você pode abri-las e continuar o trabalho por conta própria.
|
|
|
|
## Lembre-se
|
|
|
|
- Os prompts de novas sessões retornam imediatamente por padrão. Acompanhe a sessão no OpenChamber ou peça ao agente para verificá-la mais tarde.
|
|
- Um worktree separado só é criado quando você pede. As alterações não commitadas do worktree atual não são copiadas.
|
|
- A ferramenta não pode excluir sessões ou worktrees, registrar caminhos de projetos, executar comandos de shell arbitrários nem acessar URLs arbitrárias.
|
|
|
|
## Ativar ou desativar a ferramenta
|
|
|
|
Abra **Configurações → Geral → Ferramentas do OpenChamber** e altere **Ferramenta de controle para agentes**. A configuração entra em vigor quando o servidor OpenCode gerenciado reinicia, o que o OpenChamber oferece como **Apply & Restart**.
|
|
|
|
A ferramenta não está disponível quando o OpenChamber se conecta a um servidor OpenCode externo por `OPENCODE_HOST` ou skip-start, nem na extensão do VS Code. As instalações desktop e web que usam o servidor OpenCode gerenciado pelo OpenChamber têm suporte automático.
|
|
|
|
## Relacionado
|
|
|
|
- [Tarefas agendadas](/pt-br/scheduled-tasks/)
|
|
- [Sessões de worktree](/pt-br/worktrees/)
|
|
- [Objetivos de sessão](/pt-br/session-goals/)
|
|
- [Painel do navegador](/pt-br/desktop-browser/) — a ferramenta OpenChamber Web, para ver uma página e conduzi-la
|