Extension Builder

Setup

Choose the Claude model that generates your extensions, and provide an API key.

STEP 1 OF 6 · SETUP

agentClaude Code

Model

API key Kept only in this browser (localStorage), sent per-project, never saved server-side.

Remembered in this browser — revisit any time to change it.

What should this extension do?

Plain language is fine. The agent reads the attachments for the details.

STEP 2 OF 6 · REQUIREMENT

Requirement Mention the operations you need. Ambiguity becomes a question rather than a guess.

API material

Drop files here or browse

Postman · OpenAPI · PDF · Markdown · sample payloads · reference extension zip

Uploaded into the project workspace under resources/.

Analysis usually takes 2–4 minutes.

A few things the docs didn't settle

Everything else was answered by your collection.

STEP 3 OF 6 · CLARIFICATIONS

from clarifications.json

nameWhat should the extension be called?

Why I'm asking: this becomes the catalog title, the Gradle artifact, and the Java class name.

catalogWhere should this extension live in the catalog?

Why I'm asking: pick an existing Krista ecosystem/domain, or name new ones — this becomes the extension's real catalog location. Nothing is created in Studio yet; that happens once you approve the plan.

Ecosystem

Domain

authWhat authentication does this API use?

Why I'm asking: pick every mechanism this API actually supports — e.g. check both if it accepts either an API key or OAuth2. If picked alongside a real mechanism, "None" and "Not sure" are ignored. Pick "None" alone only if this API genuinely needs no credentials (a public/offline endpoint).

Authentication type(s)

API key / bearer token OAuth 2.0 — client credentials (service-to-service) OAuth 2.0 — interactive login (user authorizes) Basic auth (username/password) None (no authentication / offline) Not sure — let the agent decide from the docs

quick-setupMulti-tenant (Quick Setup) credentials — Microsoft products only

Why I'm asking: only relevant if this is a Microsoft/Office 365 product built on Microsoft single sign-on. If Krista has registered a multi-tenant Azure AD app, its Client ID and Client Secret go here so the extension's "Quick Setup" (Krista-managed sign-in) actually works — leave both blank otherwise (Quick Setup will still appear in the Authentication tab per the SDK's fixed UI, but only "Your Own Credentials" will function). Ignored for non-Microsoft extensions.

Multi-tenant Client ID

Multi-tenant Client Secret

Everything else was answered by your collection.

Review the plan

Nothing is generated until you approve this.

STEP 4 OF 6 · PLAN REVIEW

from implementation-plan.json

What should change? Sent into the same agent session for a replan — the analysis is not repeated.

Generating

You can close this tab — the run continues and the log survives a reload.

STEP 5 OF 6 · GENERATING

agent.log

… elapsed 00:00 turns 0

Streaming GET /events (server-sent events).

Built

STEP 6 OF 6 · ARTIFACTS

from build-report.json

Workspace kept for re-runs.