HN Explorer

Show HN: Dynamic code and feedback walkthroughs with your coding Agent in VSCode (intraview.ai)

48 points by cyrusradfar ↗ HN
I've been programming since I'm 6 and I don't want to quit. Since Agents came into existence I've been increasingly building more of the random ideas.

BUT, like many I kept getting stuck and frustrated where I wanted to make changes with the Agent that I knew I could've made without it but I had *no clue* how things worked.

I created Intraview to help me build and maintain a mental model of what I was building (or had vibed) so I could use my knowledge to either fix it myself, or provide more directed instruction. It grew into something that's transformed my workflow in a pleasant way.

Intraview is a VS Code extension that allows you to create: - Dynamic code tours built by your existing Agent - Storage and sharing of tours (it's a file) - Batch Feedback/commenting inline in IDE in-tour and without (it's also a file)

Here's a video walkthrough for the show vs tell crowd where I jump in a random (Plotly JS) open source repo and build a tour to get started: https://www.youtube.com/watch?v=ROBvFlG6vtY

Talking tech design, this is very different than most because the whole App is cloudless. Not server less, there's no external APIs (outside basic usage telemetry).

  - basic TypeScript app, JS/CSS/HTML
  - Localhost MCP server inside VS Code (one per workspace open)
Three of the biggest challenges I faced was:

  - re-considering the user experience given there's no database 
  - trying to build a reasonable experience to manage MCP connection across so many different setups.
  - testing the many forks, Agents and themes because I wanted to make it look native (I'll probably reverse course here in future iterations)
What I'm curious about is, where do you see the value:

  - New project/developer onboarding 
  - PR reviews 
  - Keeping up with Agentic code 
  - Perf reviews (for EM), you could build a tour biggest contributions by a GitHub handle
  - Planning alignment and review with your Agent
You can see the extension page in VS Code with these custom links (Note: this redirects and requires permission to open VS Code, won't actually install, takes another click)

  - for VS Code: https://intraview.ai/install?app=vscode
  - for Cursor: https://intraview.ai/install?app=cursor
Once it's installed and you confirm MCP is connected to your local server, just ask your Agent:

  - Create an Intraview the onboarding for this app..
  - Let's use Intraview to gather my feedback on [whatever you created]. Break down steps such that I can provide good granular feedback.
Looking forward to your feedback and discussion.

And because this is HN. A relevant quotable from PG.

  “Your code is your understanding 
  of the problem you’re exploring. 
  So it’s only when you have your code 
  in your head that you really understand
   the problem.” 
  
  — Paul Graham

8 comments

[ 0.40 ms ] story [ 26.1 ms ] thread
jay_devs
Gave this a spin and this is really cool! Wish I could provide more in-depth feedback to help improve it but will certainly be keeping an eye on it! Nicely done!
cyrusradfar
Hi @jay_devs! Thank you.

> 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.

rcarmo
Hmmm. Why Claude Code and not Copilot?
mayahisali
Hi, Good job, I have two questions:

- The cloudless architecture is intriguing. How do you handle tour synchronization when multiple devs are working on the same codebase? - How do you handle tour updates when the underlying code changes? Auto-invalidation or manual refresh?

Thanks

mock-possum
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.
joshribakoff
I see value in backfilling missing / obtuse documentation, i also see potentially negative value if used instead of improving or reading existing docs. Ideally Plotly would have a developer guide that is higher quality than what an LLM can dervive.