Upgraded Help Assistant

When you are signed in, the in-app help assistant now reads your partners, flows, mappings and transactions and answers your questions about what you have open, instead of answering from the documentation alone.

Impact: a question like “why is this flow not picking up files”, asked from that flow’s page, now gets an answer about that flow and its partner’s connection rather than a general explanation of flows. The assistant is on the Chat tab of the help panel, which opens from Help in the sidebar.

What it reads and how it answers:

• It uses the same read tools as the tedi CLI and the MCP server, and it runs them as you. It sees partners, connections, envelopes, webhooks, flows, mappings and their version history, implementations, sources, transactions, traces, results, processing logs and the feed.
• It is read-only. It cannot submit documents, resend a transaction or change configuration. When the fix is a configuration change, it tells you where in the app to make it.
• Each question carries the page you asked it from. On a partner, flow, mapping, connection, envelope, webhook, implementation, transaction or trace page, it reads that record first and follows the ids in it to related records, such as a partner’s flows or a transaction’s trace. On a list page it reads the list. From the dashboard or settings, it asks which record you mean.
• It separates what it read from what it inferred. “Your ACME partner has no outbound webhook” is a read; “that is probably why nothing arrived” is marked as a guess.
• The conversation follows you from page to page and survives a reload. A divider in the transcript marks each place you moved to a different page. New conversation starts over, and Markdown downloads the transcript.

On a transaction or trace with errors, the assistant tells you which node failed and what the error says, then points you to Diagnose Errors for the root cause. That button reads the output data of the failed nodes, which the assistant does not. Once a diagnosis exists, the assistant reads it before answering about those errors.

Diagnose Errors now reads configuration as well. Before, it saw the trace and nothing else, so it could tell you a mapping produced an empty BEG02 but not what the JSONata said. It now reads the flow that ran, the partner and its connection, and the mapping, implementation and source behind a transformation, and it names what it read in the diagnosis.

Limits:

• The conversation lives in your browser only, capped at the last 20 messages. It is cleared when you sign out and does not follow you to another browser.
• Questions are capped at 2,000 characters.
• Sources live inside the mapping editor and have no page of their own, so the assistant knows only the mapping when you ask from there. It can still read the source if you ask about it.
• The documentation-page assistant at tediware.com/resources is unchanged. Without a sign-in it has no account access and declines questions about a specific account.

The assistant is described in the tools docs.

This update was written with AI assistance. It has been reviewed and edited by a human.