A program of your own names what its agent loads, then starts a host. This is the coding agent's whole Program.cs, as it runs in the terminal. The call at the bottom is all the code it takes.
using LouisAgent.Core.Web;
using LouisAgent.Core.Anthropic;
using LouisAgent.Core.Ollama;
using LouisAgent.Core.OpenAi;
using LouisAgent.Core.Telemetry;
using LouisAgent.Core.Hosting;
using LouisAgent.Cli;
using LouisAgent.Coding;
// Usage: louis-agent.coding-cli [prompt]. It loads what this demo's catalogue names.
await CliHost.RunAsync(args, CodingCatalog.Create(), new HostServices(WebAccess.Create, OtlpTelemetry.Instance,
Providers: [AnthropicProvider.Instance, OllamaProvider.Instance, OpenAiCompatibleProvider.Instance]));The catalogue is the list of identities and packs a program can load. The coding agent's names three identities and nine packs. The host lends the rest, which is web access, telemetry and the model providers.
You write the program, its catalogue, your identities and your settings. The engine, the hosts and the packs are the framework's. Today your project references them from this repo, and packaging them for NuGet is planned.
Program.csCodingCatalog
Yours. The program starts a host, and the catalogue names the identities and packs it loads.identity/config/
Yours too. Who your agent is, as markdown you can read, and the settings it runs with.louis-agent.corelouis-agent.cli
The framework's. The engine runs the loop, and this host puts it in the terminal.packs/tools/
Ready-made packs. Each one is something an agent can do, and you name it in your catalogue or leave it out.Each program reads the settings in its own config folder, and the first place that sets a name wins. With the .NET 10 SDK installed, three steps get the coding agent answering.
your shell
What is set already wins, so one run can switch, as LLM_PROFILE=ollama dotnet run does..env.secrets
Your keys, kept out of git..env
The demo's settings..env.{LLM_PROFILE}
The model's own, such as .env.ollama or .env.anthropic, read last.demos/louis-agent/config/.env.example to .env beside it, and .env.secrets.example to .env.secrets.ANTHROPIC_API_KEY in .env.secrets, or pick a local model through Ollama with LLM_PROFILE=ollama.demos/louis-agent/hosts/louis-agent.coding-cli, type dotnet run. Its launch profile points it at the demo's config/ folder.Once it answers, change who it is, give it tools of your own, or put it on a website with a chat. Each guide walks one of those through, start to finish.