// LIVE
実Live - Tōshi at work synthetic data · no customer info
The real extension running on a sample WebCenter project. Everything here is made up - generic names, a demo company - so this is exactly the tool, on nobody's data.
Open Tōshi on any WebCenter page and she reveals what it's built from - every dashboard, saved search and task, nested as it really is on the page, each one a click from its editor. On a task page a pinned TASK row names its task type and links straight to it; land on a project's dashboard and a thin strip (or B) jumps you straight into the project, past the dashboard; from a project or task page another strip links you straight to its history, and on a history page one click expands every truncated entry. On a workflow's editor canvas a strip (or M) reads the whole canvas into a legible node-link map - every step at its real position, every transition drawn; the References view draws the same way (V), where a dashboard shared by 2+ parents stands out as a hub - and either map exports to Miro as a customer-facing wiring diagram. And when something's off, the Support bundle view exports a full support package - the reachable diagnostics (health checks, system info, host OS and system history) and the real server logs (server.log, SEVERE.log, catalina.log from WebCenter's Site Service), trimmed to a log window you pick and wrapped in a branded report.html support opens in any browser. And when a task's workflow has gone into error, one press builds a support-ready workflow-error recap - the real error message, the failed node in plain terms, the execution path in readable node names and a screenshot - ready to copy as a ticket or download as a bundle. Stop hunting the system to find what's in front of you.
The real extension running on a sample WebCenter project. Everything here is made up - generic names, a demo company - so this is exactly the tool, on nobody's data.
A WebCenter page is a stack of nested dashboards, embedded saved searches and task pages - and nothing on screen tells you which is which or where to edit them. The old reflex was to dig through the dashboard manager and guess. Tōshi reads the page you're already on and lays the structure bare. And when a page misbehaves, the same panel exports a one-press support package - the environment and the real server logs from WebCenter's Site Service, as a branded report.
Scoped to the page you opened it on - the dashboards/searches/task actually rendered, nested by their real DOM structure. Not a whole-instance crawl, just this page.
Each dashboard and search name links straight to its editor
(dashboard.jsp?…&edit=1, the saved-search editor, …). See it, click it, edit it.
One toggle and every dashboard script on the page shows up nested under its dashboard - display and run scripts, each with its Dashboard Context (Project / Document / Task / My Work) and type (visibility, on change, validation, …). The logic behind the glass, not just the layout. On a page thick with scripts, filter by context and type: the chips start greyed, click one to light it up and the list narrows to just those scripts. Hover a script row and it lights up its exact target: a bound field, its layout block - so a tab-visibility script highlights just that tab - or, for a saved-search display-script, the one results column it paints, header and every value cell, not the whole search.
Open it in two browser windows, ten tabs, whatever - they never collide. Tōshi injects fresh on the page you're looking at and keeps no shared state, so there is nothing to clear, ever. Inspect one project in one tab and another beside it - each reads its own page, with no stale overlay carried over and nothing to reset between them.
Tōshi is a lean Chrome extension - it injects only when you click its icon
(activeTab + scripting, no host permissions).
One click, straight from the Chrome Web Store. No need to ask anyone for a link, just add it and open a WebCenter page.
One small thing. If you install Tōshi, a quick heads-up to me is genuinely appreciated. It is completely optional and not needed to use it, but knowing someone is running it means a lot.
Tōshi is a Manifest V3 extension built on Chromium APIs -
chrome.scripting with a MAIN-world probe and a shadow-DOM panel. The line is
simple: any Chromium browser that loads an unpacked MV3 extension runs her; Gecko and WebKit
would need a port.
| Browser | Engine | Status | Notes |
|---|---|---|---|
| Google Chrome | Chromium · Blink | ✓ full | Primary target - every build is tested here. Load unpacked from chrome://extensions. |
| Microsoft Edge | Chromium · Blink | ✓ full | Same MV3 + chrome.scripting + MAIN-world probe. Load unpacked from edge://extensions. Often the sanctioned Chromium browser on a locked-down corporate laptop. |
| Brave | Chromium · Blink | ✓ full | Identical engine and APIs. Load unpacked from brave://extensions. |
| Opera · Vivaldi · Arc | Chromium · Blink | ◐ works | Chromium siblings - load-unpacked behaves the same. Not part of the tested set, but no reason she wouldn't run. |
| Firefox | Gecko | ✕ not as-is | MV3 differs - the browser.* namespace, a non-service_worker background, and newer/limited MAIN-world injection. Would need a port. |
| Safari | WebKit | ✕ no | Requires converting to a Safari Web Extension via Xcode - no load-unpacked. Not on the roadmap. |
Rule of thumb. If the browser has an …://extensions page with a
Developer mode toggle and Load unpacked, Tōshi runs - that's every Chromium browser.
Where Chrome is locked down on a corporate machine, that usually means Edge.
The panel reads top to bottom in four zones: a title bar (identity + panel chrome), a slim instance bar, then the view switch, a filter + Pick band, and a Show strip - above the tree. Each control is a single, focused action; active toggles glow blue.
[bracketed] ids. Off by default - you rarely need them while scanning. Filtering still matches ids even when hidden.skipDashboard=1, every other parameter kept; from a task page it opens the task's own project (projdetails.jsp?skipDashboard=1, rebuilt from the task's projectID and menu_file), dashboard skipped. It hides once you've skipped, or on any other page, so it's never in the way.... in turn. Tōshi finds every truncation toggle and expands it, so the full audit trail is there to read or copy in a single action - replacing the old bookmarklet.name [id].chrome://extensions/shortcuts. Single letters stay scoped to the panel, so they never clash with WebCenter or the browser.The same visual language you'll see in the panel.
Open Tōshi on a task whose workflow went into error and press Build recap. She assembles it all at member level - no admin: the actual error message read from the workflow token audit (e.g. Template with name _ProjTmp not found), the failed node in plain terms (e.g. Create Project) with its internal id kept for support, the full execution path in human-readable node names, and the error-minute timeline from project history - status changes, the failing rule / JS action, attribute writes - plus a screenshot. Then Copy ticket for a paste-ready summary, or Download bundle for report.html + screenshot + recap.json. Detection is precise: a normal task, or a rule-engine failure that never touched the workflow, is not flagged.
On a workflow's editor canvas, press Workflow map (or M). The canvas is pixels - a stack of HTML5 <canvas> layers whose node model the page never exposes - so Tōshi goes to the source: it fetches the workflow XML (DownloadWorkflowXML.jsp) on your session and parses the topology - nodes, transitions and their real editor coordinates. It draws an SVG map (no libraries): every node a box at its true position, coloured and glyphed by type - Start, User task, Approval, Auto task, Sub-workflow, JavaScript, Router, Error / System-error, End - transitions drawn as labelled arrows, error routes dimmed, any dangling or foreign node flagged. Hover a node to light its links; Fit the whole shape to the panel, then Export a Markdown / JSON handover (a node table + a transition table).
The same engine draws the References view as a node-link graph (toggle Tree ↔ Graph, key V): each dashboard, saved search and task / approval dashboard a node, references the edges. A dashboard referenced by 2+ parents reads as a shared hub - an emphasis ring and a ×N badge over a clean layered layout, the one thing the tree can't show - with deleted / dangling references kept flagged. And ◈ Miro exports either map as a customer-facing wiring diagram: the Miro layout DSL (node-type → shape / colour / labelled connector) that KG / Claude (miro-workflow-kata) draws onto a board - Tōshi writes the file, it doesn't draw the board. Read-only on WebCenter - the only write is the export.
Dashboards (blue) and searches (green), nested by their real structure. Names link to editors.
A slim bar under the header reads the live WebCenter version and host of the instance you're on - so you always know which environment you're inspecting. Read once, from your own session.
Type and the matched text lights up on the actual hits - ancestors stay dim for context, so you see exactly what matched.
Click an element on the page; its row is marked in the list and the element keeps a blue glow on the page. One selection, persistent.
Outline everything at once, panel stashed. Every label is a link (↗) to its editor - the map doubles as a launchpad.
On a task page Tōshi shows a single pinned TASK row at the top of the panel: it names the task type and links straight to its task type page, so you know at a glance what task page you're on. The type is resolved via GetProjectTasks (the same call the WCR Inspector used); the task itself isn't outlined on the page. Works on the modern task execution page (wctaskexecutionpage.jsp), where there is no task form - the id is read from the page URL.
Every action has a key while the panel is focused. Press ? for the cheat-sheet; toggle Tōshi from anywhere with Alt+Shift+T (rebindable). Single letters stay scoped to the panel, so they never clash with WebCenter or the browser.
The Support bundle view (key L) exports a complete support package for the session - a health battery (WebCenter's troubleshooting tests: DB, disk, app-server round-trip, workflow engine, CAD-X), system info, host OS and system history, plus the real server logs from WebCenter's Site Service (siteconfig.jsp / DownloadLogfiles.jsp): server.log, SEVERE.log and catalina.log, the large ones (SEVERE.log can run to hundreds of MB) linked and the rest embedded. You pick a log window (15 minutes to all, filtered by level) and Tōshi trims every log client-side - anchored to each log's newest line, so timezones never matter - merges them into one chronological incident.log, and leads with a branded report.html: instance, version, a colour-coded error count and a deduped error roll-up, the read-first triage page support opens in any browser. All in one version-stamped .zip, built with the browser's own compression. No upload, no login, no extra permission.
A three-way segmented switch at the top of the controls picks what fills the panel. On page is the default (what's in front of you); Support bundle is the one-press diagnostics export; References is the deep dependency map.
The dashboards, searches and task page actually rendered on this page, nested by DOM containment - a parent is the nearest ancestor that's also inspectable. When the task's workflow has errored, a workflow-error recap pins to the top of the panel. No network calls. Scoped to what you can see.
The middle segment. One click gathers the reachable WebCenter diagnostics on your current session - health battery, system info, host OS and history, and the real server logs - trims them to a log window and exports a branded report.html inside one version-stamped .zip. Read-only on WebCenter.
Walks each on-page dashboard's full LOADDASHBOARD config - every dashboard it
links to, recursively (sub / button / task / approval + embedded searches), cycle-safe, with
DELETED dashboards flagged. The deep dependency map - opt in when you want it.
productinfo), so you never mistake which environment you're inspecting. Hidden on a non-WebCenter page.chrome://extensions/shortcuts. Single letters stay scoped to the panel, so nothing clashes with WebCenter or the browser.GetProjectTasks) and links both its general-info page and its specifications/execution page. The Default vs Task Execution view is chosen from that page's own Current View dropdown - it switches in place, so there is no separate URL.The recent releases, most recent first. Tōshi tells you in-panel when she updates, and this page is where that link lands.
Project history, in the panel. The ◷ Project history strip now does more than link out: a plain click pulls the project's whole audit trail straight into Tōshi - every event, who did it and when, newest first. Filter by free text over every column, or by category chips (approval / document / task / status / member / attribute, each counted, positive selection), then ⤓ Export the currently-filtered rows as a titled Markdown handover doc - project, host, WebCenter version, capture time, the table, the active filter - or Shift for JSON. What you see is what you hand over. Read-only on WebCenter; the strip still opens WebCenter's own history in a new tab on a middle / Ctrl-click.
Support-bundle logs tail-capped. Each log file the Support bundle reads is now capped to its last 4 MB before trimming - a very large SEVERE.log can no longer balloon a single pull. The window filter (15 min to all, by level) still runs on top, anchored to the newest line.
Project-history quick link. On a project page or a task execution page, a thin strip now links straight to that project's history (history.jsp?type=project, targeted by the page's own projectID) - a real link, so middle / Ctrl-click opens it in a new tab.
Expand all history. On a WebCenter history page, one click opens every truncated ... entry at once, so the full audit trail is there to read or copy in a single action - replacing the old bookmarklet.
Workflow Error Recap. Open Tōshi on a task whose workflow went into error and press Build recap: she assembles - all at member level, no admin - the real error message from the workflow token audit, the failed node in plain terms (id kept for support), the full execution path in legible node names, an error-minute timeline from project history and a screenshot, then Copy ticket or Download bundle (report.html + screenshot + recap.json). Detection is precise: a normal task, or a rule-engine failure that never touched the workflow, is not flagged.
Skip-dashboard from a task page too. The skip-dashboard strip (and the B key) now also fires on a task execution page: it opens the task's own project with the dashboard skipped, rebuilding the project link from the task's own parameters. On a project landing page it works exactly as before.
Skip-dashboard jump. On a project's dashboard landing page a thin amber strip (or the B key) takes you straight into the project, past the dashboard - it only shows on that landing page and steps out of the way once you've skipped.
The in-panel What's New strip itself. A quiet one-line strip at the top of the panel after an auto-update, with a short highlight of what changed and a link to this page. Dismissible, silent on first install, and shown once per version.
The Support bundle skips the slow login-tracking step on prod.
The Support bundle view decluttered, with the filter, pick and show controls hidden while a bundle is gathering.
Tōshi grows on her own track (透 I-XII), from "sees this page" to "reads any WebCenter and hands you the map nobody wrote down." What's live today, and what's next.
零Born · 27 Feb 2026 - where the eye first opened
Last updated: 2026-07-24
GetProjectTasks) - each one click from its editor.DownloadWorkflowXML.jsp) and draws an SVG graph, every node at its real editor position, typed and coloured, transitions labelled, error routes dimmed, dangling / foreign nodes flagged. Outbound: the References reference graph now renders as the same node-link diagram (toggle V) where a dashboard referenced by 2+ parents stands out as a shared hub (ring + ×N badge); and ◈ Miro exports either map as a customer-facing wiring diagram - the Miro layout DSL that KG / Claude (miro-workflow-kata) draws onto a board. A deliverable, not just a debug view.