siclark

It did.. the model was teh same, but the prompts the user gave, and so the journey that they took was different to mine. When we brought the knowledge back together it was really interesting, we had a better solution than if I had tried to build out the model and do the analysis myself.

We were researching how to build a model to predict sewage levels in a river that we teach kayaking on.

But also it helped my friend who is less familiar with prompting some good techniques.. he could read my thought process on how I prompted.

A few extra points I have considered / know about.

Obsidian - Why not just use Obsidian. This works as an Obsidian vault out the box if thats how you want to use it. Summaries use wikilinks so works with the graph view. What this adds is the orchestration and getting data out of the raw conversation in vscode in multiple locations. It captures the journey as well as the outcome.

Why no embeddings / RAG - My pain wasnt searching notes, it was ongoing research and analysis and sharing that live with a friend or colleague without needing to construct a db.

Followups. Single transport per machine constraint. Already in testing and plan to move that to config per workspace.

Happy to chat more if anyone thinks this is useful.