tesseract-agent 0.11.34 → 0.11.36

package/dist-bundle/builtin-skills/continue-from-another-agent/SKILL.md

@@ -2,12 +2,12 @@
 name: continue-from-another-agent
 description: Pick up work that another agent, framework or conversation started — a conversation moved here from another framework, an earlier Tesseract conversation, a session in Claude Code, Codex, Gemini CLI, Cursor or another agent's own app, or a hand-off note — by finding and reading what was done, rebuilding the state, checking it against the project as it is now, and continuing from the exact stopping point. Also for writing a hand-off for the next agent, and for bringing another agent's memories, skills and connectors into Tesseract.
 license: MIT
-version: 1.1.0
+version: 1.1.1
 metadata:
   tesseract.summary: Find what another agent or conversation did, verify it against the project now, and carry on from there.
   tesseract.category: software
   tesseract.examples: "continue what I was doing in Codex yesterday | pick up where my last Claude Code session stopped | write a handoff so another agent can finish this | कल दूसरी चैट में जो काम शुरू किया था, उसे आगे बढ़ाओ | أكمل المهمة التي بدأها وكيل آخر"
-  tesseract.tools: sessions_search, sessions_read, memory_read, memory_write, app_extensions
+  tesseract.tools: sessions_search, sessions_read, memory_read, memory_write, app_extensions, crew_handoff
 ---
 
 # Continue from another agent
@@ -100,7 +100,11 @@ Ask one focused question only when the stopping point or the intended next step
 ## Writing a hand-off for the next agent
 
 When the person asks for one, or before they move the work elsewhere: write it in the conversation, or in
-a file they choose (not committed unless asked). Include the five points of step 2, the commands to verify
+a file they choose (not committed unless asked). Start from `crew_handoff` (reached with `tool_call`): it
+drafts one from what Tesseract recorded of a session's work, not from what was said — what it was asked,
+the files it changed and its commits, the commands it ran and how each ended, its plan, its leases and what
+it waits on — and `keep` writes it to a Markdown file. Another session of this project can draft one for
+any session here too. Then add what only you know. Include the five points of step 2, the commands to verify
 the current state, the decisions and their reasons, and anything still running (jobs, watches, scheduled
 tasks — with their ids). Write it for a reader with no history: absolute paths, exact commands, no "as
 discussed". Moving this conversation itself to another framework is the person's choice in its framework

package/dist-bundle/builtin-skills/tesseract-help/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: tesseract-help
 description: Answer questions about Tesseract itself and operate the app for the person — what it can do and how, settings and appearance, engines, models and run modes, API keys, skills, plugins and MCP connectors, machines, OS permissions, updates, the guided tour, troubleshooting a stuck or broken app, and filing a bug report. Use whenever the question or request is about the Tesseract app rather than the person's own work.
-version: 1.0.7
+version: 1.0.8
 metadata:
   tesseract.summary: Answer questions about Tesseract and change its settings, engines, extensions and connectors for the person.
   tesseract.category: tesseract
   tesseract.examples: "switch the app to dark mode | how do I connect an MCP server to Tesseract | the background service seems stuck, can you fix it | एजेंट का डिफ़ॉल्ट मॉडल कैसे बदलूँ? | ماذا يستطيع Tesseract أن يفعل، وكيف أشغّل الوضع الصوتي؟"
-  tesseract.tools: tesseract_capabilities, app_list_capabilities, app_describe, app_settings, app_navigation, app_engines, app_providers, app_runners, app_runtimes, app_extensions, app_hosts, app_account, app_daemon, app_image, app_voice, app_permissions, app_project, app_privacy, app_system, app_fonts, app_present, app_tour, submit_issue, skill_find
+  tesseract.tools: tesseract_capabilities, app_list_capabilities, app_describe, app_settings, app_navigation, app_conversations, app_engines, app_providers, app_runners, app_runtimes, app_extensions, app_hosts, app_account, app_daemon, app_image, app_voice, app_permissions, app_project, app_privacy, app_system, app_fonts, app_present, app_tour, app_studio, submit_issue, skill_find
 ---
 
 # Tesseract help
@@ -31,10 +31,10 @@ in your own list, find it with `tool_find` and run it with `tool_call`.
 
 ## 2. Doing it — App Control
 
-Each domain has one tool that takes `{action, input}`: `app_settings`, `app_navigation`,
-`app_engines`, `app_providers`, `app_runners`, `app_runtimes`, `app_extensions`, `app_hosts`,
-`app_account`, `app_daemon`, `app_image`, `app_voice`, `app_permissions`, `app_project`,
-`app_privacy`, `app_system`, `app_fonts`, `app_present`, `app_tour`. The full map with notes:
+Each domain has one tool that takes `{action, input}`: `app_settings`, `app_navigation` (the window),
+`app_conversations` (the conversations in it), `app_engines`, `app_providers`, `app_runners`, `app_runtimes`,
+`app_extensions`, `app_hosts`, `app_account`, `app_daemon`, `app_image`, `app_voice`, `app_permissions`,
+`app_project`, `app_privacy`, `app_system`, `app_fonts`, `app_present`, `app_tour`, `app_studio`. The full map with notes:
 [references/app-control-map.md](references/app-control-map.md).
 
 1. **Explain or do?** "How do I…" → explain, and offer to do it. "Do / change / turn on…" → do it.
@@ -43,17 +43,22 @@ Each domain has one tool that takes `{action, input}`: `app_settings`, `app_navi
 3. Prefer the specific action (`settings.set_theme`) over the generic patch (`settings.set`).
 4. Not sure of the fields? `app_describe` — do not guess.
 
-**App Control has no confirmation step — every action happens immediately.** So *you* ask first,
+**The run mode gates App Control like any tool**: reading always works; a change is refused in Chat and Plan and
+asked about in Default — but in Full access it **happens immediately**. So *you* ask first,
 in one plain sentence, before anything destructive, costly or hard to undo: removing a machine
 (`hosts.revoke`), signing out (`account.logout`, `engines.logout`), changing the plan
 (`account.set_plan`), erasing data (`privacy.erase_data`, `system.clear_habits`), uninstalling or
 removing anything (`extensions.uninstall_*`, `extensions.remove_mcp_server`, `runtimes.remove`,
 `runners.remove`, `providers.remove_credential`, `present.delete_deck`), importing browser
-passwords (`privacy.browser_import_run`), or loosening the agent's own limits (run mode, budget,
-gateway policy).
-
-To **show** the person something, open it: `navigation.open_settings`, or a link to one panel —
-`tesseract://settings/<section>` with `appearance`, `editor`, `runners`, `agent`, `extensions`,
+passwords (`privacy.browser_import_run`), closing a conversation the person is using (`conversations.close`), or
+loosening the agent's own limits (run mode, budget, gateway policy). A conversation's access is never yours to
+widen: `conversations.set_run_mode` narrows it (a stricter mode, internet off) but refuses Full access, internet on
+and keep going when away — send the person to the mode menu in that conversation's composer.
+
+To **show** the person something, open it: `navigation.open_settings {section}` (general, appearance, shortcuts,
+runners, agent, voice, extensions, account, perks, team, privacy, remote-desktop, network, about),
+`navigation.open_tab`, `navigation.open_file` — then `navigation.state` says what is in front. Or write a link to one
+panel — `tesseract://settings/<section>` with `appearance`, `editor`, `runners`, `agent`, `extensions`,
 `voice`, `image-edit`, `search`, `account`, `team`, `general`, `shortcuts`, `about`,
 `permissions`, `privacy`, `hooks`, `env`, `background-tasks`, `sync`, `file-drops`,
 `remote-desktop`, `network`. Written as a markdown link it is clickable:
@@ -85,6 +90,10 @@ To **show** the person something, open it: `navigation.open_settings`, or a link
 | Machines, copying projects, mirroring | `hosts.list`, `hosts.copy_project`, `hosts.start_mirroring` |
 | Mic, screen recording, accessibility, full-disk access | `permissions.status` → `permissions.request` or `permissions.open_settings` (some need a relaunch) |
 | Updates | `system.updater_state`, `system.check_for_updates` |
+| Open, start, rename, fork or close a conversation; move one to another framework or model | `conversations.list` (session ids, which one is yours) → `conversations.*` |
+| Open a file, a screen, a panel, a new window; split, zoom, full screen | `navigation.*` — `navigation.state` first and after |
+| The app looks broken after a theme | `navigation.set_safe_mode {on: true}` (strips every extension's theming), then `extensions.*` to remove the pack |
+| Inspect the app's own UI | `navigation.toggle_devtools` (Tesseract's window); a web page: the browser tools |
 | "Show me around" | `tour.start` (building tours: the `tutorials` skill) |
 | Presentations | the `stage-deck` skill (`app_present`) |
 | A custom font | `fonts.list` → `fonts.create` (ready in a few minutes in the Fonts tab) |

package/dist-bundle/builtin-skills/tesseract-help/references/app-control-map.md

@@ -2,7 +2,8 @@
 
 Call the domain's tool with `{action: "<id>", input: {…}}`. `app_describe {ids: [...]}` returns
 the exact fields of any action; `app_list_capabilities {domain|query}` lists them. ⚠ marks actions
-to confirm with the person first (App Control itself never asks). "R" = read only.
+to confirm with the person first (the run mode asks only in Default; in Full access nothing does). "R" = read only —
+it runs in Chat and Plan too.
 
 ## settings — `app_settings`
 - `settings.get` R — the whole settings object.
@@ -13,10 +14,25 @@ to confirm with the person first (App Control itself never asks). "R" = read onl
 - `settings.has_search_key` R — whether web search works on this install (it is brokered; there is no personal key).
 - `settings.set {patch}` — generic merge into settings (top-level keys: appearance, editor, agent, general, voice, engine, terminal, imageEdit, notifications). Last resort; read `settings.get` first and patch only the key you mean.
 
-## navigation — `app_navigation` (needs an app window)
-`navigation.open_settings`, `open_search` (command palette), `open_agents` (machines), `go_home`,
-`toggle_terminal`, `toggle_tasks_rail`, `toggle_state_rail`. A specific Settings panel: the link
-`tesseract://settings/<section>`.
+## navigation — `app_navigation` (the window; needs the app open on this machine)
+- `navigation.state` R — the project, the view, the tab in front, every tab open, the Settings page if open, which panels show.
+- `navigation.open_settings {section?}` (general, appearance, shortcuts, runners, agent, voice, extensions, account, perks, team, privacy, remote-desktop, network, about).
+- `navigation.open_tab {tab: home|files|settings|computers|community|team|vault|remote-desktop|stage|fonts|whats-new|image-search|report-issue}` (team = Atrium).
+- `navigation.open_file {path}` (the app's editor/viewer), `open_browser {url?}`, `open_panel {panel: conversations|files|terminal}`.
+- `navigation.split {direction: right|down}`, `close_tab` (the tab in front — never your own conversation), `reopen_closed_tab`.
+- `navigation.new_window {folder?, session_id?}`, `zoom {action: in|out|reset}`, `full_screen {on?}`.
+- `navigation.toggle_devtools` — the inspector on Tesseract's own window (a web page: the browser tools).
+- `navigation.set_safe_mode {on}` — strips every extension's theming; the way back from a broken theme.
+- Older toggles: `open_search` (command palette), `open_agents` (machines), `go_home`, `toggle_terminal`, `toggle_tasks_rail`, `toggle_state_rail`.
+
+## conversations — `app_conversations` (the conversations in the window)
+- `conversations.list` R — each one's `session_id`, title, framework, model, mode, running, in front, and `yours`.
+- `conversations.new {message?, framework?, model?, focus?}` — a first message is sent as the person would.
+- `conversations.open {session_id, title?}` — one in the window, or a saved one (find it with `sessions_search`).
+- `conversations.rename {session_id?, title}`, `conversations.fork {session_id?, title?}` — yours when no id.
+- `conversations.set_run_mode {session_id?, framework?, model?, effort?, mode?, internet?, keep_going?}` — a framework change moves it there with its history. Access only narrows: Full access, internet on and keep going are the person's.
+- ⚠ `conversations.close {session_id}` — leaves the window (a running turn stops); kept, `open` brings it back. Not yours.
+- `conversations.stop {session_id}` — stops another conversation's turn.
 
 ## engines — `app_engines`
 - `engines.list` R — engines with install/auth/model. Use ids exactly as it returns them.
@@ -65,7 +81,7 @@ Write: `copy_project {from_host, to_host, src_path, dest_name}` (background; ret
 `workspace_link_start` / `stop`, ⚠ `revoke {device_id}`.
 
 ## account — `app_account`
-`account.me` R; `update_profile`; `request_password_reset {email}`; `join_waitlist`;
+`account.me` R; `update_profile`; `request_password_reset {email}`;
 ⚠ `logout`; ⚠ `set_plan {plan, interval}` (billing). Plan names shown in the app differ from ids:
 `standard` is shown as "Pro", `pro` as "Team".
 

package/dist-bundle/builtin-skills/tesseract-help/references/troubleshooting.md

@@ -30,8 +30,7 @@ by name, delete `~/.tesseract` or settings files, or reinstall the app on your o
 ## Things the product deliberately does not do
 
 Before calling something a bug, check `tesseract_capabilities` §18 ("Deliberately NOT built") —
-for example there is no public sign-up (accounts are invite-only), no team-chat voice messages,
-and no VPN tunnel a user can turn on yet. Say so plainly instead of trying workarounds.
+for example there are no team-chat voice messages and no VPN tunnel a user can turn on yet. Say so plainly instead of trying workarounds.
 
 ## When it is a Tesseract bug