Show HN: Dynamic code and feedback walkthroughs with your coding Agent in VSCode

> Wish I could provide more in-depth feedback to help improve it

I've got updates on this thread here, email me at support at v1 d0t co, or you can tell your agent to write up/synthesize your thoughts and submit feedback to intraview (assuming you have the extension installed).

If you're saying you don't have time -- totally get it and no presh! You made a builders day by giving it a go.

Given we're all here to learn, I'll share more details on the testing matrix:

IDE: VSCODE, Cursor, Windsurf, Cline, Roo

Agents: Claude Opus/Sonnet/Haiku, OpenAI GPT-5/GPT-5-codex-[low|med|hi], etc...

Theme: Then when you hit UI, if you use themes there's at four that are very common including default light/dark modes.

Tours are stored as a flat file (JSON). When you open a tour, you open it with the Agent and on, re-opening, it goes through re-validation (as is done during the tour). In the case where lines shift in files because the file includes start/end ranges and line text (verbatim), this will cause the tour to be invalidated and the Agent will need to rebuild it. There are a lot of "dead code" cases where this won't catch a tour update, today.

The tour file contains a ton of meta information, as well, so each time the Agent opens it -- it could rebuild the tour with the same intents. The original user request, synthesized request, success criteria, concepts that are going to be taught.

This is a first pass solution for now. If there's more interest, there's a much more interesting tech solution with managing pointers to references and invalidating the tour on a broader range of criteria.

Part of what I need to learn is:

  - A. Are tours something that folks use as ongoing "interactive" documentation, e.g. a set of onboarding tours
  - B. Are tours ephemeral that folks use to hash out how to approach a feature, bug or review a PR.

Your thoughts are welcome and appreciated. Have a lovely Friday.

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.

I'm solving may be for folks like me who would prefer to have the guide IN CODE. It's a new experience to me as I've never used an in IDE code tour.

I think what I'm experiencing is it's way more helpful for me to have the guide navigate through code so I can explore a little at each step and get a lay of the land.

How people learn is personal, and what I hoped for when I was building this was more of an experience where I'm walking through with a teammate.

I considered trying to have a voice AI read or explain each step. I also considered allowing another person to drive your IDE through mirroring what they're looking at. Both were cut at the idea phase because it felt it was feature bloat on a concept that I didn't know anyone (but me) really wants

Open to any more ideas or feedback! Thank you so much for dropping in