Ops Engineer · Posted 18 days ago
The Context Explorer feature would really help me debug why Jarvis pulls certain files into a session and ignores others. Saw a reference to it in a release note. What's the ETA and what exactly does it do?
Founder, CEO
Context Explorer gives you a visual view of: (1) what files Jarvis loaded into the session, (2) why each was loaded (manifest topic match, relationship graph neighbor, or explicit tool call), and (3) which parts of each file it actually used in its response.
Currently behind a feature flag in Business plan tenants. Rolling out to Pro in ~3 weeks pending a couple of UI fixes. DM me if you want it turned on for your tenant early.
Ops Engineer
Turned on for our tenant, been using it for 3 days. This is the debugging tool I didn't know I needed. Caught a manifest that had the wrong topic tag and was pulling in unrelated files.