init

solwyn init takes a repository from nothing to a working, budget-verified setup in one pass. It resolves a credential, picks a project, writes your configuration, detects which provider SDKs your code imports, prints the exact wiring for each, and confirms the whole chain by reading your budget back from Solwyn Cloud. It never asks for or stores a provider API key — every provider credential stays on your own client.

solwyn init [--agents] [--run-cap <usd>]

Run it from anywhere inside your repository. Provider detection and — with --agents — the files it writes are anchored at your Git root, so the location within the repo does not matter.

What it does, in order

$ solwyn init
Field                                                                      Value
Project                                                            proj_0123456789abcdef01234567
Configuration                                                            written
Providers                                                                 openai
SDK wiring                    import openai; from solwyn import Solwyn; client =
                               Solwyn(openai.OpenAI(api_key="<OPENAI_API_KEY>"))
Budget verification                                                     verified
Budget remaining                                                           75.00
Utilization                                                               25.00%

The wiring it prints

Each snippet wraps the client you already construct — Solwyn is a wrapper, not a proxy, so your calls still go directly to the provider. The CLI prints each snippet as a single line; they are expanded here for readability.

from openai import OpenAI
from solwyn import Solwyn
client = Solwyn(OpenAI(api_key="<OPENAI_API_KEY>"))

from anthropic import Anthropic
from solwyn import Solwyn
client = Solwyn(Anthropic(api_key="<ANTHROPIC_API_KEY>"))

from google import genai
from solwyn import Solwyn
client = Solwyn(genai.Client(api_key="<GOOGLE_API_KEY>"))

import boto3
from solwyn import Solwyn
bedrock = boto3.client("bedrock-runtime", region_name="<AWS_REGION>")
client = Solwyn(bedrock)

from solwyn import Solwyn
client = Solwyn(<YOUR_PROVIDER_CLIENT>)

For OpenAI and Anthropic, the CLI matches the snippet to how your code already imports the SDK — module-style (import openai) or symbol-style (from openai import OpenAI).

Running non-interactively

init is safe to run in CI, but it cannot prompt there, so both interactive steps have a non-interactive failure mode. The other ways it can stop are listed alongside:

Provide SOLWYN_API_KEY and --project (or SOLWYN_PROJECT_ID) and init runs straight through with no prompts. These exit codes are drawn from the frozen set. If --run-cap fails after the project was created, the project and its stored key survive; the config file is not written, and stderr tells you to review the new project's rules before retrying.

Writing agent guidance with --agents

$ solwyn init --agents

--agents additionally writes agent-facing guidance so coding assistants use Solwyn's guardrails correctly. It writes exactly three files, all carrying the same canonical guidance:

The write is transactional — all three files land together or none does, and a failure rolls back to the prior state. It is idempotent — re-running replaces the marked AGENTS.md section in place rather than appending a second copy, and refreshes the two standalone files. Your existing AGENTS.md content outside the markers is left untouched, byte for byte. If another process edits one of the targets mid-write, the CLI preserves that edit rather than clobbering it, rolls back its own changes, and exits 1 with agent_artifact_recovery_required naming the retained backups. The atomic-exchange primitives it relies on exist on Linux and macOS only; on Windows, --agents fails with agent_artifact_write_failed.

Next steps

• Authentication — credential types, storage, and the precedence init follows
• Configuration — what lands in config.toml and how to change it
• Agents — wiring Solwyn's guardrails into agent loops
• budget rules — the runaway-run cap --run-cap creates, and how to add one to an existing project
• Privacy — why detection and wiring never expose your prompts or keys