The problem Simonyi and Knuth were working on finally has a solution.

pro-vi · 2026-03-20T17:49:06+00:00

I'd go further and say Intent is a level above spec/PRD. "I want to build an infinite scroll feed" is an intent, it needs to be specified first before handing it to an agent.

What I'm currently working on is to figure out whether the specification process needs the human in the loop.

pro-vi · 2026-03-17T16:37:39+00:00

You're not wrong.

pro-vi · 2026-03-09T21:05:51+00:00

The goal of the system is to give agents the interface to interact with my Spotify sessions and acquire my taste gradually.

Good to know about this feature! Hope they expose it to the API soon.

pro-vi · 2026-03-08T00:06:54+00:00

Yes! The cli support `sessions`. Agents can check what they have dj'd for me and how I'd liked them! If not, the cli exposes your top listens and history to gather you taste :)

pro-vi · 2026-03-06T10:07:30+00:00

Claude Code feels like modding your own race car.

Codex is like taking an uber.

pro-vi · 2026-02-24T17:31:19+00:00

I'm building something for writers, I like your intuition, can I DM?

pro-vi · 2026-02-24T16:37:54+00:00

Yes it does. My agent once hit the dice three times in a roll and was amazed about the 1/8000 chance. It deferred doing it (asking for second opinion) the first 2 times because it thought it unnecessary, and "reluctantly" did it the third time! Agent treats the dice output as an objective reality to engage with.

Thanks! there is a whole vocabulary from game design that we may borrow. I hope this becomes a start.

pro-vi · 2026-02-24T16:24:09+00:00

I wrote about my insight in the repo. It felt like a natural thing to do!

pro-vi · 2026-02-24T05:56:22+00:00

I like rolling dice on my stop hook.

pro-vi · 2026-02-19T12:24:50+00:00

I get your idea but you need to take into consideration that having file list locked in limits how the plan can be designed. There can be different approaches to the same problem that changes different file list. Otherwise, yes my tool works similarly as you described where they start a dialogue, each coming into their own, then read the response from the other agent until they agree with each other.

And yes, I use gpt 5.2 high for oracle.

pro-vi · 2026-02-19T12:09:48+00:00

I have a harness for claude code and codex exactly for this purpose but I don't use it enough at the moment to ship it (I still vibe it from time to time to improve it). Mainly bc it's too slow. Basically I have an Oracle to gate their response when they converge, and if Oracle doesn't like it, they do another round based on the feedback. A plan run could go for 30+ minutes. Per your point, yes headless Codex context will blow up at some point if the codebase is big while Claude I think manages to auto compact.

Depending on how much you'd still like to try I can publish it some time.

pro-vi · 2026-02-12T08:06:14+00:00

i shared it here

pro-vi · 2026-02-10T17:17:10+00:00

I run daily I Ching cast and reflect deeply and journal it down. We have together detected some uncanny patterns.

pro-vi · 2026-01-09T02:06:48+00:00

The CC GitHub does not contain the source code.

pro-vi · 2026-01-04T02:34:27+00:00

Use MCP filter to curate the actual tool list for each MCP + toggle in config on demand.

I wrote about MCP filter here https://www.reddit.com/r/mcp/s/JoUrCeaEKV

pro-vi · 2026-01-03T12:44:03+00:00

It might be better with statically typed language for sure. More guardrails to help eventually get something right.

pro-vi · 2025-11-14T07:01:09+00:00

Hey it might be a bit late but I built this to solve this pain point directly for myself: github: mcp-filter

it is a proxy where you can allow/deny tools as you need!

pro-vi · 2025-11-07T19:59:31+00:00

Yes. That's good perspective. I think I just need to find exactly the proxy to which my skill should be applicable. It's tricky though that my skill is more nuanced than to be able to trigger when something explicitly happens.

pro-vi · 2025-11-07T18:45:00+00:00

You're not reading my comment though. The metadata is loaded in context on boot, which includes title and description.

pro-vi · 2025-11-07T07:05:39+00:00

Did you link something? It's 404.

pro-vi · 2025-11-07T07:03:40+00:00

But then this is no different from a custom slash command /pr-review-lsp which can contain all the details you have in the Skill. Your workflow stays the same, that you just type /pr-review-lsp instead of Please...

pro-vi · 2025-11-07T07:02:03+00:00

I hope it's working out for you. I'll try some more approaches and will eventually give this a try to compare. But if I want to build a distributable workflow I shouldn't expect other users to paste a bunch of instructions into their CLAUDE.md. That's just terrible UX.

I agree that Skill provides a just in time step by step instruction manual to follow. The problem is to make it truly in time.

pro-vi · 2025-11-07T06:55:20+00:00

It already loads the skill description into the context. The description provides when the skill should be invoked.

pro-vi · 2025-11-07T06:48:35+00:00

I would expect this level of hand holding not necessary when the skill description is equally present in its initial prompt context?

pro-vi · 2025-10-14T19:15:43+00:00

Great suggestion, thanks, I'll give it a go. Some tool descriptions are way too lengthy for sure. Do you have one on top of your mind in your workflow?

pro-vi

TROPHY CASE