Brief in progress — review the script and demo before recording.
This session is about managing knowledge and setup that is harness-agnostic and covers everything durable agents need to make as many decisions as possible without human involvement. They also have to be able to reach the right person when needed.
- Configuration: the setup should not be over-engineered. We can show some Markdown templates and an Obsidian-like knowledge system that works as a wiki for both agents and humans.
- Environment: we should show how centralization (a VPS or a dedicated machine) helps with managing ambient agents. That does not necessarily mean everything has to be centralized, but knowledge about the setup should be — at the end of the day, ambient agents have to be managed by other agents.
- Knowledge Delivery: the problem with most knowledge bases is that they quickly become outdated. That is less true with agents, especially when they work with templates and dynamic templates (the agent decides on the structure, but within some rules, rather than a rigid structure).
- Operations: ambient agents will operate from system prompts, profiles, and skills that evolve over time, often improved semi-autonomously. All of this has to be versioned, with an easy way to roll back. Git is the obvious choice, but not the only one — platforms such as Langfuse can extend this, so agents and a given setup can be evaluated.
We may want to showcase scenarios such as:
- A setup that starts simple and can self-evolve and self-heal over time. This can be achieved fairly easily through centralization and foundations that leave agents free to modify every aspect of the system.