Skip to content

The seven Tessa tools the page did not mention - #122

Merged
ETWOYA merged 2 commits into
mainfrom
docs/tessa-tools-complete
Oct 2, 2026
Merged

ETWOYA merged 2 commits into
mainfrom
docs/tessa-tools-complete

Conversation

@dankoverride

Copy link
Copy Markdown
Collaborator

The page listed 13 tools. 20 are registered for the 3D client.

Everything below was verified at its registration site, not inferred from class names — AddCoreTools, AddWebTools and the Unity bootstrapper.

Missing from core

Tool Registered by What it does
Feedback AddCoreTools Send feedback about a tool, a response or Tessa — bug, suggestion, quality, performance, UX, praise
WebPost AddWebTools HTTP POST to a URL, returning status, headers and body
GetPreferences Unity client Read preferences, and which are hers to change
SetPreference Unity client Change a preference, for the agent-writable subset

A whole capability the docs were silent on

MakeShoebox, RunShoebox, ShareShoebox. A shoebox is a Mermaid diagram of services calling each other plus a run of it, built from a description — the user never chooses a language or a stack.

RunShoebox takes a repeat count, which is how you watch an intermittent failure happen exactly once rather than every time. That isn't a detail anyone would guess, so the page says it.

WebPost is the one I would not have shipped undocumented

It is the only tool on the page that writes anywhere other than the user's own machine. It is allowlisted by host via WebTools:AllowedPostHosts, and the page now states both the capability and the limit.

A claim corrected while here

The page said these tools are available "on every DeepCube surface". Six of the twenty are registered by the Unity client specifically, so that was never true of the whole list. It now says these are the 3D client's tools and that other surfaces register their own — which is what I can actually demonstrate.

Also noted that SetPreference reaches only the agent-writable subset, with the excluded ones named (redaction, sign-in, the frame budget), linked to the preferences page where that list lives.

🤖 Generated with Claude Code

The page listed thirteen tools. Twenty are registered for the 3D client.

Missing from core, all verified at their registration sites rather than inferred
from class names:

  Feedback      AddCoreTools. Sends feedback about a tool, a response or Tessa,
                categorised as bug, suggestion, quality, performance, UX, praise.
  WebPost       AddWebTools. HTTP POST to a URL, returning status, headers and
                body. For driving an API, not reading a page.
  GetPreferences, SetPreference
                Registered by the Unity client. Read preferences and change the
                subset marked agent-writable.

And a capability the docs were silent on entirely. MakeShoebox, RunShoebox and
ShareShoebox: a shoebox is a Mermaid diagram of services calling each other, plus
a run of it, built from a description without the user choosing a language or a
stack. RunShoebox takes a repeat count, which is how you watch an intermittent
failure happen exactly once rather than every time -- worth saying, because it is
not a detail anyone would guess.

WEBPOST IS THE ONE I WOULD NOT HAVE SHIPPED UNDOCUMENTED. It is the only tool on
the page that writes anywhere other than the user's own machine. It is
allowlisted by host through WebTools:AllowedPostHosts, and the page now says both
things.

CORRECTED A CLAIM WHILE HERE. The page said these tools are available "on every
DeepCube surface". Six of the twenty are registered by the Unity client
specifically, so that was never true of the whole list. It now says these are the
3D client's tools and that other surfaces register their own, which is what I can
actually show.

Also noted that SetPreference reaches only the agent-writable subset, with the
excluded ones named, and linked to the preferences page where that list lives.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@dankoverride
dankoverride requested a review from ETWOYA as a code owner October 2, 2026 01:52
@ETWOYA
ETWOYA merged commit 926a9e3 into main Oct 2, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants