@andreprado/agentkit 0.1.0-alpha.2 → 0.1.0-alpha.4

package/src/templates/index.ts

@@ -1,4 +1,5 @@
 import { blankTemplate } from "./blank";
+import { dentistaTemplate } from "./dentista";
 import { supportTemplate } from "./support";
 
 export type TemplateFile = {
@@ -17,6 +18,7 @@ export type AgentTemplateContext = {
 
 const templates = new Map<string, AgentTemplate>([
   [blankTemplate.name, blankTemplate],
+  [dentistaTemplate.name, dentistaTemplate],
   [supportTemplate.name, supportTemplate],
 ]);
 

package/src/templates/support.ts

@@ -63,6 +63,7 @@ node_modules/
         contents: `# Optional: add real provider keys after switching away from test/fake.
 OPENAI_API_KEY=
 ANTHROPIC_API_KEY=
+OPENROUTER_API_KEY=
 `,
       },
       {
@@ -194,28 +195,37 @@ Start building immediately:
 - Edit \`prompts/instructions.md\` for support behavior.
 - Edit \`agentkit.config.ts\` for provider, tools, secrets, access, and storage.
 - Add or replace TypeScript tools under \`tools/\` when the requested support agent needs actions or external data.
+- Do not wait for a wizard or recipe. AgentKit provides the scaffold and contract; you decide the implementation from the owner's brief.
 - Ask follow-up questions only when missing information blocks a safe local implementation.
 - State assumptions in the final response.
 
 ## Local Commands
 
-- \`npm install\`: install capsule dependencies.
+- \`npm install\`: restore capsule dependencies if this capsule used \`--no-install\`, install failed, or \`node_modules\` was deleted.
 - \`npm run chat -- --message "hello"\`: send one local chat message.
 - \`npm run agentkit -- tool lookup_order --input '{"orderId":"A100"}'\`: test the example tool directly.
 - \`npm run eval\`: run agent evals.
 - \`npm run dev\`: run the local Agent Capsule runtime.
 - \`npm run agentkit -- inspect\`: print machine-readable capsule state.
-- \`npm run agentkit -- env set <NAME> <VALUE>\`: write a local secret value to ignored \`.env\`.
+- \`printf %s "$VALUE" | npm run agentkit -- env set <NAME> --stdin\`: write a local secret value to ignored \`.env\` without putting it in shell history.
 - \`npm run agentkit -- env list\`: list local secret names without printing values.
 - \`npm run agentkit -- docs full\`: print the full AgentKit contract path.
 
+## Testing With A UI
+
+- Local UI: run \`npm run dev\`, open the printed \`Chat:\` URL, and tell the owner the exact URL.
+- Hosted UI: after \`npm run agentkit -- deploy\`, run \`npm run agentkit -- chat-ui --deploy\`, open the printed \`Chat:\` URL, and tell the owner it is connected to the hosted deploy.
+- \`test/fake\` is deterministic. It is useful for scaffold checks, direct tool checks, and fake-provider evals, but it does not validate natural conversation quality.
+- Before claiming real conversation behavior is tested, ask the owner which provider to use: OpenRouter, OpenAI, Anthropic, or another supported provider. Do not choose for them.
+
 ## Hosted Deploy
 
 - Local scaffold, chat, eval, dev, inspect, tool, and build commands are token-free.
 - Hosted deploy requires an invited AgentKit Cloud alpha token. If no token is stored yet, ask the owner for one and run \`npm run agentkit -- login --token <token>\`.
-- Put production secret values into managed secrets with \`npm run agentkit -- secret set <NAME> <VALUE>\`, not into committed files.
+- Put production secret values into managed secrets with \`npm run agentkit -- secret set <NAME> --from-local-env\`, \`--from-env\`, or \`--stdin\`, not into committed files or shell history.
 - Deploy with \`npm run agentkit -- deploy\`, then check \`npm run agentkit -- deploy status\`.
-- Create client-facing deploy access tokens with \`npm run agentkit -- access token create <name>\` when a website or app needs to call the hosted agent.
+- Hosted deploy writes the local chat/UI deploy access token to \`.agentkit/chat-access-token.json\`. Create extra client-facing tokens with \`npm run agentkit -- access token create <name> --out <path>\` when a separate website or app needs its own credential.
+- Use \`npm run agentkit -- deploy --smoke "hello"\` or \`npm run agentkit -- deploy smoke --message "hello"\` for an official hosted chat smoke check.
 - Do not run operator/admin commands from a user capsule.
 
 ## Files
@@ -251,27 +261,52 @@ Turn the request into a working local capsule:
 - Update \`agentkit.config.ts\` when tools, secrets, provider, or access rules change.
 - Add, replace, or remove TypeScript tools under \`tools/\` for real actions or external data.
 - Keep the first version runnable with \`test/fake\` unless the owner explicitly asks for a real provider.
+- Do not use a wizard or recipe. Build the capsule directly from the scaffold, the AgentKit contract, and the owner's brief.
 - Make practical assumptions and list them in your final response.
 - Ask follow-up questions only when missing information blocks a safe local implementation.
 
 ## Local Commands
 
 \`\`\`sh
-npm install
 npm run typecheck
 npm run agentkit -- inspect
 npm run agentkit -- tool lookup_order --input '{"orderId":"A100"}'
 npm run eval
 \`\`\`
 
+\`test/fake\` proves the scaffold and deterministic tool paths. It does not prove natural conversation quality.
+
+\`agentkit new\` installs dependencies by default. Run \`npm install\` only if the capsule was created with \`--no-install\`, install failed, or \`node_modules\` was deleted.
+
 Set local development secrets without opening code:
 
 \`\`\`sh
-npm run agentkit -- env set OPENAI_API_KEY "<value>"
+printf %s "$OPENAI_API_KEY" | npm run agentkit -- env set OPENAI_API_KEY --stdin
 npm run agentkit -- inspect
 npm run chat -- --message "hello"
 \`\`\`
 
+## Testing With A UI
+
+Local UI:
+
+\`\`\`sh
+npm run dev
+\`\`\`
+
+Open the printed \`Chat:\` URL and tell the owner the exact URL.
+
+Hosted deploy UI:
+
+\`\`\`sh
+npm run agentkit -- deploy
+npm run agentkit -- chat-ui --deploy
+\`\`\`
+
+Open the printed \`Chat:\` URL and tell the owner this local UI is connected to the hosted deploy.
+
+Before claiming real conversation behavior has been tested, ask the owner which provider to use: OpenRouter, OpenAI, Anthropic, or another supported provider. Do not choose for them. After they choose, update \`agentkit.config.ts\`, \`.env.schema\`, local secrets, hosted secrets if deploying, then rerun chat/UI checks.
+
 If you add a tool, also run a fake-provider tool smoke test:
 
 \`\`\`sh
@@ -305,9 +340,10 @@ This capsule is deploy-ready by default.
 1. Keep tools edge-safe and use \`ctx.db\` instead of importing database drivers.
 2. Run \`npm run agentkit -- build\` only when you want to validate the artifact locally.
 3. If the owner has not logged in yet, ask for an invited AgentKit Cloud alpha token and run \`npm run agentkit -- login --token <token>\`.
-4. Put production secrets into managed secrets with \`npm run agentkit -- secret set <NAME> <VALUE>\`.
+4. Put production secrets into managed secrets with \`npm run agentkit -- secret set <NAME> --from-local-env\`, \`--from-env\`, or \`--stdin\`.
 5. Run \`npm run agentkit -- deploy\`.
-6. Create client-facing deploy access tokens with \`npm run agentkit -- access token create <name>\` when a website or app needs to call the hosted agent.
+6. Run \`npm run agentkit -- chat-ui --deploy\` to test the hosted agent through a local UI using the auto-created \`.agentkit/chat-access-token.json\`. Create extra client-facing deploy access tokens with \`npm run agentkit -- access token create <name> --out <path>\` when a separate website or app needs its own credential.
+7. Use \`npm run agentkit -- deploy --smoke "hello"\` during deploy or \`npm run agentkit -- deploy smoke --message "hello"\` afterward for an official hosted smoke check.
 
 AgentKit owns hosted infrastructure and production secrets. Do not put production secret values in this capsule. Do not run operator/admin commands from a user capsule.
 `,
@@ -321,6 +357,7 @@ Use AgentKit conventions when editing this support capsule.
 - The agent contract lives in \`agentkit.config.ts\`.
 - The example tool lives in \`tools/lookup-order.ts\`.
 - The default provider is \`test/fake\`, which can call tools from JSON messages during local tests.
+- Ask the owner which real provider to use before switching from \`test/fake\`; do not choose OpenRouter, OpenAI, or Anthropic automatically.
 - Keep required local secret names in \`.env.schema\` and values in ignored \`.env\`. AgentKit local commands load \`.env\` directly.
 - Treat the owner's natural-language request as the brief and start implementing inside this capsule.
 `,
@@ -334,14 +371,18 @@ Generated by AgentKit as a support Agent Capsule.
 ## Setup
 
 \`\`\`sh
-npm install
 npm run chat -- --message "hello"
 npm run agentkit -- tool lookup_order --input '{"orderId":"A100"}'
 npm run eval
 npm run dev
 \`\`\`
 
+\`agentkit new\` installs dependencies by default. Run \`npm install\` only if this capsule was created with \`--no-install\`, install failed, or \`node_modules\` was deleted.
+
 The support template includes a local \`lookup_order\` TypeScript tool and uses \`test/fake\` by default.
+\`test/fake\` does not validate real conversation quality. The owner must choose OpenRouter, OpenAI, Anthropic, or another supported provider before real model behavior is tested.
+
+For UI testing, run \`npm run dev\` and open the printed \`Chat:\` URL. After hosted deploy, run \`npm run agentkit -- chat-ui --deploy\` and open its printed \`Chat:\` URL.
 `,
       },
     ];