weirdguy

4 ms·

1. 1.▲
   by weirdguy 2mo ago

   UPD: Looked into burr from dagworks deeper, it's actually a good target to support the codegen for, will investigate today and add into the scope of upcoming things. Thank you for showing those things!
2. 2.▲
   by weirdguy 2mo ago

   The codegen side is target-agnostic on purpose, LangGraph is just the first target. Burr (thanks for educating about that piece of tech) could be a good N-one, its state/transition model maps onto the spec real pretty. Vercel's ev
3. 3.▲
   by weirdguy 2mo ago

   Good question For hosted agents only, a Terraform provider probably makes sense. The reason I didn’t start there is that Kastor has two paths: 1 - build: compile the spec into framework code, e.g. LangGraph 2 - plan/apply for agents ho
4. 4.▲
   by weirdguy 2mo ago

   I agree with you don't think the "agent" abstraction is stable enough to standardize the behavior/runtime layer yet. thing I'm trying to test is smaller: is that possible to standardize the outer contract around age
5. 5.▲
   by weirdguy 2mo ago

   try with www, should work, the apex zone still did not propagate for whatever reason
6. 6.▲
   by weirdguy 2mo ago

   thanks — that’s the direction. current version is still just validate + LangGraph codegen, but plan/apply/state is the part I’m trying to get to next
7. 7.▲
   by weirdguy 2mo ago

   oh, it's not, just root domain (non-www) without redirect
8. 8.▲
   by weirdguy 2mo ago

   hey HN, it's first time posting something here. I’m building Kastor: Go CLI/declarative language/config for AI agents. the motivation: agent definitions often end up spread across framework code, prompt files, tool files&#x2F
9. 9.▲
   Show HN: Kastor – Terraform-style specs for AI agents(github.com)

   33 points by weirdguy 2mo ago|21 comments