Migration: pkg/chat extracted to the go/chat module¶

The multi-provider AI chat client has been extracted from go-tool-base into the phpboyscout/go language subgroup as a standalone, SDK-free module plus one module per provider:

Documentation now lives at chat.go.phpboyscout.uk.

What go-tool-base did¶

go-tool-base/pkg/chat is now a thin adapter that:

• re-exports the module's public types/constructors (chat.Config, chat.New, chat.Tool, …), so existing GTB call sites are unchanged;
• owns the GTB Viper config-key schema (ConfigKeyClaudeKey, ConfigKeyAIProvider, …) and the SettingsFromProps / NewFromProps / NewWithFallbackFromProps adapters that map Props into the module's typed Settings;
• blank-imports all three provider modules, so every provider is registered — GTB tools keep working with every provider with no import changes.

The chat core source (~4,400 lines) was deleted from the tree; only the adapter remains.

What you need to do¶

If you consume GTB's pkg/chat (e.g. chat.New, chat.Config, the config-key constants): nothing — the adapter re-exports the same API and links every provider.

If you want the light, framework-free client directly (no go-tool-base): import the module and opt into only the provider(s) you use:

import (
    "gitlab.com/phpboyscout/go/chat"
    _ "gitlab.com/phpboyscout/go/chat-anthropic" // activate "claude"
)

client, err := chat.New(ctx, chat.Settings{
    Config: chat.Config{Provider: chat.ProviderClaude, Token: apiKey},
})

The module is config-system-agnostic: supply credentials via Config.Token, Config.Credentials, or the well-known env vars — the GTB Viper config schema stays in go-tool-base's adapter. See chat.go.phpboyscout.uk for the full API, provider matrix, and the core↔provider version-compatibility rules.