HackerTrans
トップ新着トレンドコメント過去質問紹介求人

avyvar

no profile record

投稿

[untitled]

1 ポイント·投稿者 avyvar·24 日前·0 コメント

[untitled]

1 ポイント·投稿者 avyvar·25 日前·0 コメント

Show HN: Context-drop – CLI tool to to share files/images between remote agents

github.com
1 ポイント·投稿者 avyvar·2 か月前·0 コメント

[untitled]

1 ポイント·投稿者 avyvar·2 か月前·0 コメント

Show HN: SkillFS – Git-backed persistent sandboxes for AI agents

github.com
4 ポイント·投稿者 avyvar·6 か月前·0 コメント

コメント

avyvar
·2 か月前·議論
how so? we have two options - one with a public link url (i.e something like a Mintlify site with llms.txt, and the LLM searches directly). We only expect folks to upload publicly available docs for now, but would love to hear any potential other solutions for more private docs!
avyvar
·2 か月前·議論
Totally fair question. If you only want one agent to sanity-check one doc change, a skill/prompt is probably enough.

We actually aren’t rebuilding a harness here, it’s Pi with several LLM options to select from. The reason this is a project is that the useful workflow is more like a docs test suite: run realistic user tasks across multiple models, isolate each run in a greenfield sandbox, keep the transcripts/results, and make failures reproducible in CI.

You could ask an existing coding agent to spawn subagents for every task/model pair, but once that matrix grows, running hundreds of subagents on your computer gets messy. It’s also the wrong isolation boundary: for docs testing, you usually want the agent to start from a clean environment with access only to the docs/product surface you’re testing, not your whole working tree or local setup.