Vihren is being built as an Agent Development Kit for Go teams on Temporal: a library for building agents and agent harnesses where the agent loop, tools, memory, human review, sandboxed execution, testing, and observability are designed as durable workflow primitives.
I am looking for design partners because those primitives should be shaped by real production workflows, not by guessing at abstractions in isolation.
Most agent frameworks start with prompts and tools, then add durability, retries, human review, and operations afterward. Vihren starts from the other end: Temporal is already good at long-running state, signals, retries, and crash recovery. The goal is to make agent systems fit that model without hiding Temporal behind an opaque runner.
Who should talk to me
You run Temporal in Go, or you are actively moving a Go service onto Temporal.
You have workflows that span hours, days, or weeks and wait on people, external systems, retries, or audit-sensitive decisions.
You are adding LLM-assisted or tool-using steps to those workflows.
Temporal is infrastructure for your product, not the product itself. You do not want to maintain a private agent-harness layer forever if the common pieces can become a supported open-source library.
The exchange
You bring a real workflow and its constraints. I help map it onto the current Vihren and Temporal foundation, identify the missing agent-harness primitives, and turn the reusable parts into open-source Vihren work.
The best fit is a real workflow where LLM-assisted steps are forcing hard questions about durability, human review, tool execution, memory, sandboxing, testing, or observability.
This is not “install Vihren and everything is solved.” The current release is early. The point of working together is to design against production pressure: human waits, crash recovery, observability gaps, workflow-specific testing, sandbox boundaries, and the places where LLM-assisted steps need explicit control.
The boundary is simple: the work should improve the open-source Vihren platform, not become a private fork.
Contact
Email [email protected] with a short description of your Temporal workflow, the Go service it lives in, and the human wait, failure mode, tool step, or LLM-assisted decision that is forcing you past ordinary request/response code.