Huh wow usually I’m pretty skeptical about stuff like this but your video demo looks pretty neat, I’m gonna try it on my our codebase at work today and see how it goes! We’ve moved fast and broken stuff lately and struggled a bit to come up with coherent contributing guidelines, in addition to onboarding new devs and guiding LLM codegen - it’d be cool if a tool like this could help elucidate the key things you need to know to work within our bespoke framework.
Ah, shucks! Thank you. Means a lot to me to have folks giving it a go. I recognize how much our attention is strained these days.
I'm trying to figure out whether folks really want this as more of a documentation tool for onboarding, or for "on-the-fly" transient digging: bugs/root cause, PR Review support, co-designing, or code style review across a section. The inline feedback is what's been clutch and sticky for me both within tours, and outside.
If you have feedback and install it or have issues you can email me at support at v1 d0t co --
If it's more of an idea, feature request, or potential bug you can ask your agent (once MCP is connected) to "Send feedback to intraview team" or something similar to be clear you don't want to add feedback for the Agent (which it can also do) and it'll send us a Slack message.
hey I got to play around with it a bit in vscode, and my main takeaway is - the content is generates is good, and the experience of taking a tour/walkthrough is a positive one - but the UI for actually generating and launching tours feels a bit wonky.
I could only get the MCP to work via Claude, not Copilot or Codex - and I couldn't find an easy way to get back to the 'setup' screen where it provides the config, so I had to keep resetting the extension so that that prompt would come back up - removing that friction seems essential, if the initial configuration doesn't work, then getting back to that screen is a necessity
I feel like I'm missing a GUI button to launch a tour/walkthrough - asking the LLM to do it for me feels weird, when the markdown file is sitting right there. I'd much rather just right-click a markdown file, and select "Intraview: Launch Tour" or something.
I'm less of a terminal guy, so this appearing to lack a solid GUI, or integration with the GUI of my IDE, is discouraging for me personally. But the fact that it generates solid info is encouraging, and the process of giving feedback and refining the walkthrough steps also feels (and works) pretty good.
I'd probably wait til there's a little more polish before playing with it again, but I'll keep it in mind! Cool thing!
My next release is focused on having a sidebar UI and launcher that'll probably make some of your issues go away. This would allow you to
Really appreciate the thoughtful feedback. Thank you!Following up:
Double clicking on something you said, "I could only get the MCP to work via Claude, not Copilot or Codex" -- did you mean that getting it to actually connect or having the Agent use the MCP properly after it's connected.