القائمة
Configuring CORS for TypeScript HTTP endpoints. Use when the user asks to enable CORS, allow cross-origin requests, or configure allowed origins for HTTP endpoints.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Migrating a TypeScript Golem agent from the OLD decorator/base API (@agent + BaseAgent) to the fluent (Standard Schema) defineAgent API. Use when porting an existing decorator-based TS agent, when you see @agent()/extends BaseAgent/@endpoint/@description code that no longer compiles, or when asked to modernize a TS component to the current SDK.
Adding a new TypeScript agent to a Golem component. Use when the user asks to create, add, or define a new agent type, implement an agent class, or add agent methods in a TypeScript Golem project.
Adding typed configuration to a TypeScript Golem agent. Use when the user asks to add config, settings, or parameters to a TypeScript agent that can be set via golem.yaml or CLI.
Enabling authentication on TypeScript HTTP endpoints. Use when the user asks to add auth, require authentication, use Principal, or protect HTTP endpoints.
Exposing a TypeScript Golem agent over HTTP. Use when the user asks to add HTTP endpoints, mount an agent to a URL path, or expose agent methods as a REST API.
Using golem:rdbms/ignite2 from a TypeScript Golem agent. Use when the user asks to connect to Apache Ignite 2, run SQL over Ignite, or use Ignite from TypeScript agent code.
استنادا إلى تصنيف SOC المهني
| name | golem-add-cors-ts |
| description | Configuring CORS for TypeScript HTTP endpoints. Use when the user asks to enable CORS, allow cross-origin requests, or configure allowed origins for HTTP endpoints. |
Set cors on the mount options of http.mount(...) to apply allowed origins to all endpoints:
import { z } from 'zod';
import { defineAgent, method, http } from '@golemcloud/golem-ts-sdk';
export const MyAgent = defineAgent({
name: 'MyAgent',
id: { name: z.string() },
http: http.mount('/api/{name}', { cors: ['https://app.example.com'] }),
methods: {
getData: method({ input: {}, returns: Data, http: http.get('/data') }),
// Allows https://app.example.com
},
});
Pass cors in the endpoint options (the second argument to a verb builder) to add allowed origins for a specific endpoint. Origins are unioned with mount-level CORS:
export const MyAgent = defineAgent({
name: 'MyAgent',
id: { name: z.string() },
http: http.mount('/api/{name}', { cors: ['https://app.example.com'] }),
methods: {
getData: method({ input: {}, returns: Data, http: http.get('/data', { cors: ['*'] }) }),
// Allows BOTH https://app.example.com AND * (all origins)
getOther: method({ input: {}, returns: Data, http: http.get('/other') }),
// Inherits mount-level: only https://app.example.com
},
});
Use '*' to allow all origins:
export const PublicAgent = defineAgent({
name: 'PublicAgent',
id: { name: z.string() },
http: http.mount('/public/{name}', { cors: ['*'] }),
methods: { /* ... */ },
});
Golem automatically handles OPTIONS preflight requests for endpoints that have CORS configured. The preflight response includes Access-Control-Allow-Origin, Access-Control-Allow-Methods, and Access-Control-Allow-Headers headers.