The SDK

Abhed's internals live under internal/, which Go refuses to let another module import. The sdk package is the supported surface across that wall, kept small so the internals stay free to change.

import abhed "github.com/yuvrajsingh/abhed/sdk"

a, err := abhed.New(ctx, abhed.Options{
    Workspace: "/srv/work",
    Provider: &abhed.Provider{
        Type: "anthropic", Model: "claude-opus-5",
        APIKey: os.Getenv("ANTHROPIC_API_KEY"),
    },
    Mode: "auto",
    Deny: []string{"bash(rm -rf *)"},
    Approve: func(ctx context.Context, tool string, args json.RawMessage, d abhed.Decision) (bool, error) {
        return askTheUser(tool, args, d.Reason)
    },
    OnEvent: func(ev abhed.Event) { log.Println(ev.Type) },
})
if err != nil {
    return err
}
defer a.Close()

answer, err := a.Run(ctx, "fix the failing tests")

Surface

Method
`New`	build from options, a config directory, or both
`Run`, `Continue`	send a prompt; `Continue` keeps the conversation
`Steer`	redirect a run in progress, from another goroutine
`Fork`	rebuild the conversation up to a sequence number
`Events`	everything recorded; the stream is the session
`Usage`	tokens, turns, cache hit rate, compactions
`ExportHTML`	a self-contained transcript
`SetModel`	swap providers mid-conversation
`Providers`	the provider types this build supports

What does not change when embedded

Policy still decides what runs. Every action is still recorded, so an embedded session replays exactly like one from the CLI. An extension still may veto and never permit.

One difference is deliberate: an agent with no Approve function refuses anything needing approval rather than assuming yes. A service with nobody to ask should be stricter than a terminal with somebody watching, not looser.