Stats
Agents, governed: rules the model can't rewrite, approvals, budgets, and a re...
Wardrik as a daemon: agents from files, config.yaml, an HTTP API, and the war...
A durable agent runtime for Elixir. Agents survive a crash, wait for a person...
What Wardrik sends and takes: its events, as CloudEvents, and its operations,...
Wardrik in Slack: agents answer in threads, and ask there, with Approve and D...
Coding agents such as Claude Code, as tools WardrikCore agents call, over ACP.
Chat apps people reach Wardrik's agents through, such as Slack: rooms, thread...
Each agent's events as CloudEvents: a log to read back, and a stream to follow.
A durable key-value store that Wardrik packages keep their data in.
Ask agents something on a clock, when a feed has something new, or when a ser...
Web search for agents, through Brave: the passages of each page that bear on ...
A web dashboard for Wardrik's operators, mounted in a Phoenix router.
An Elasticsearch connector for Broadway
Credentials sealed at rest, for WardrikCore agents to call tools with.
Lua 5.3 for agents: a sealed sandbox, and the run_lua tool that runs code an ...
Deep research for agents: a topic split across angles, a subagent researching...
Budgets that cap what an agent spends, and rules and judges that decide every...
OAuth sign-in for WardrikCore agents, with grants kept in WardrikVault.
Rate limits, circuit breakers and model failover for agents' model calls, as ...
The tools of any MCP server, for WardrikCore agents to call.
Tools for agents from an HTTP API's description, such as a Google Discovery d...
Files for agents: a tree of their own kept in the store, trees they share, an...
Wardrik over HTTP: every operation as a JSON route, and agents' events as ser...
What a package built on Wardrik's protocol tests with: a server that runs War...