profiles

Overview ¶

profiles materializes a complete provider profile — skills, MCP, hooks, sub-agent, instructions — and then proves on disk that the selected CLI really sees it.

v1 shape (design doc §2.9): the profile is declared with two vocabulary packages and read back through two verbs on the Agent.

adaptor.New(driver,
    adaptor.WithProfile(profile.CloneNative(dir, profile.CopySettings(), profile.LinkAuth())),
    adaptor.WithProfileResources(profile.Resources{Agents: ..., Hooks: ..., Instructions: ...}),
    adaptor.WithSkills(skill.Inline(...)),
    adaptor.WithMCP(mcp.Stdio(...)),
)
ai.ProfileState(ctx)  // read-only: where the profile is and what is present
ai.SyncProfile(ctx)   // mutate: materialize the declaration, report the truth

Profile mutation stays on the Agent because it changes what a run does; Inspect() exposes only read-only panels.

Usage:

go run ./examples/profiles -agent=codex
go run ./examples/profiles -agent=claude -profile-mode=native -run

-run=true is the only mode that calls the paid CLI; everything else is local filesystem and subprocess evidence.