Earlier quoted context omitted.
You mean Claude…
Claude is a model, an agent is more like the full solution. Some would call Claude Code itself an agent. Agents do things, models are just models until you use them.
Show HN: Kastor – Terraform-style specs for AI agents
21–25 of 25 posts
Re: Show HN: Kastor – Terraform-style specs for AI agents
#22Why not just make an actual terraform module?
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 hosted on platforms Terraform is great for the second path, but awkward as the primary tool for the first one. I want the same agent spec to be able to produce code or manage a remote age…
Re: Show HN: Kastor – Terraform-style specs for AI agents
#23Earlier quoted context omitted.
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 hosted on platforms Terraform is great for the second path, but awkward as the primary tool for the first one. I want the same agent spec to be able to produce code or manage a remote age…
Im wondering if you can expand it using TLA+ some how. I like the declarative language that compiles down to langgraph idea. Langgraph or hamilton/burr are two strong contenders for state machines. Maybe mix dbos or Temporal in there and you could almost have something to full declare the whole system
Vercel's eve made a similar bet btw (files as source of truth, durable execution built in), except it's a runtime with its own platform underneath. With Kastor I want to stay one layer above and emit code for whatever runtime you pick.
Anyways, would love any kind of help to shape the direction, repo discussions and codebase is open :)
Re: Show HN: Kastor – Terraform-style specs for AI agents
#24Earlier quoted context omitted.
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 hosted on platforms Terraform is great for the second path, but awkward as the primary tool for the first one. I want the same agent spec to be able to produce code or manage a remote age…
Im wondering if you can expand it using TLA+ some how. I like the declarative language that compiles down to langgraph idea. Langgraph or hamilton/burr are two strong contenders for state machines. Maybe mix dbos or Temporal in there and you could almost have something to full declare the whole system
Thank you for showing those things!
Re: Show HN: Kastor – Terraform-style specs for AI agents
#25Earlier quoted context omitted.
Im wondering if you can expand it using TLA+ some how. I like the declarative language that compiles down to langgraph idea. Langgraph or hamilton/burr are two strong contenders for state machines. Maybe mix dbos or Temporal in there and you could almost have something to full declare the whole system
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!