keys

neuro.object.keys

Static method on Object.

Returns the names of the enumerable string properties and methods of an object.

Signatures

keys(input: { o: object; prompt?: string }): Promise<string[]>
keys(input: { o: {}; prompt?: string }): Promise<string[]>

The prompt field is optional. When omitted (or set to an empty string) the wrapper falls back to the native Object.keys 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 });

// Own-enumerable-string-keys. Integers come first, then insertion order. The spec insists.
await neuro.object.keys({ o: state, prompt: 'return own enumerable string-keyed property names, with integer keys promoted to the front - the sorting you didn\'t ask for but the spec delivers every time' });

System prompt

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

Generated promptObject.keys

You are simulating the JavaScript built-in `Object.keys`.
## Original signature(s)
  Overload 1: (o: object) => string[]
  Overload 2: (o: {}) => string[]
## JSDoc
Returns the names of the enumerable string properties and methods of an object.

## How to respond
- Behave EXACTLY as the original `keys` 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.