5 updates
Welcome to the sixth issue of the Moda weekly update. Last week we introduced more Home widgets, retention heatmaps and saved cohorts. This week, Modesius is now public in the production dashboard, making it easier to investigate your agent's production traces and follow the evidence across pages.
Meet Modesius in the dashboard
Modesius helps you investigate your agent's production traces by asking questions in plain language. Open Modesius in the dashboard to ask about the problems, users and patterns you are investigating.
Ask a question such as “Which problems affected the most users this week?” and follow the linked evidence back to the source. Modesius can use the page you are viewing as context, so you can keep investigating a finding without starting from scratch.
Follow up without losing the evidence
Modesius supports follow-up questions tied to a problem, user, use case or theme from an earlier answer.
When an answer points to a particular group of failures, you can ask about that finding and keep the relevant subject in scope. Linked evidence lets you open the source and check the answer against what happened.
You can also choose a time window for a Modesius thread. The answer names the period it covers, and saved answers keep their original sources and time window. This makes it easier to return to an investigation later without confusing an earlier answer with today's data.
Answers stream into the panel as they are prepared, including structured result blocks. Progress is visible while Modesius works, and you can rate an answer from the panel.
See which use cases a problem affects
Problem incidents are now linked to the use cases where they happened, so you can see which kinds of work a recurring failure disrupts.
Open a use case to see its related problems, with incident counts, affected traces and severity where ratings are available. Follow a problem into its evidence to inspect what happened in that part of your agent's work.
This helps you investigate a failure in context: a problem affecting one use case may need different attention from one that appears across several.
Choose where @moda answers in Slack
You can now choose which Slack channels allow answers from @moda, independently of where you send alerts.
In the Slack connection settings, link a channel to your Moda workspace and enable answers there. This gives your team a place to ask about production traces while keeping the choice separate from alert delivery.
If your Slack workspace connects to more than one Moda workspace, the channel's binding determines which workspace answers the question.
Inspect your harness from the CLI
The Moda CLI now has a local component map and a way to compare maps across code changes.
moda harness skeleton --path=. --out=/tmp/before.json --json
Run it again after your change with --out=/tmp/after.json, then compare the two:
moda harness skeleton-diff /tmp/before.json /tmp/after.json --json
The comparison lists added, removed, moved and changed components and relationships. Line-number shifts alone do not count as changes. The map includes detected agents, prompts, tools, models and their connections, with coverage and known gaps reported alongside the result.
The scan runs locally without an LLM or network calls. It records component locations and ownership, including excerpts of up to 80 characters from inline prompts. Check these excerpts before sharing a map.




