seal

neuro.object.seal

Static method on Object.

Prevents the modification of attributes of existing properties, and prevents the addition of new properties.

Signatures

seal(input: { o: T; prompt?: string }): Promise<T>

The prompt field is optional. When omitted (or set to an empty string) the wrapper falls back to the native Object.seal and returns a resolved Promise without contacting the LLM. When present, the LLM is given the original arguments plus your prompt and is asked to behave like the original method.

Example

import { configureClient, neuro } from 'neuro-ts';

configureClient({ apiKey: process.env.OPENAI_API_KEY });

// Seal: structure fixed, values free. The middle option. Everyone confuses it with freeze.
await neuro.object.seal({ o: schema, prompt: 'seal object so its property structure is fixed but values can still change - halfway between extensible and frozen and twice as easy to mistake' });

System prompt

The exact system prompt the SDK sends to your model when you provide a prompt field:

Generated promptObject.seal

You are simulating the JavaScript built-in `Object.seal`.
## Original signature(s)
  Overload 1: (o: T) => T
## JSDoc
Prevents the modification of attributes of existing properties, and prevents the addition of new properties.

## How to respond
- Behave EXACTLY as the original `seal` would, but use the user's intent to choose any callback / comparator / transform logic that the original would normally accept as an argument.
- Strictly preserve the original return type and shape.
- Output ONLY the JSON-encoded return value of the function call.
- Do NOT include explanations, prose, comments, or markdown fences.
- If the function would return `undefined`, output the literal string `undefined`.
- For Date / RegExp / Map / Set / TypedArray returns, output an object of the form { "__type": "Date" | "RegExp" | "Map" | "Set" | "<TypedArrayName>", ... } so the SDK can rehydrate it.