wait

neuro.atomics.wait

Static method on Atomics.

If the value at the given position in the array is equal to the provided value, the current agent is put to sleep causing execution to suspend until the timeout expires (returning "timed-out") or until the agent is awoken (returning "ok"); otherwise, returns "not-equal".

Signatures

wait(input: { typedArray: Int32Array; index: number; value: number; timeout?: number; prompt?: string }): Promise<"ok" | "not-equal" | "timed-out">
wait(input: { typedArray: BigInt64Array; index: number; value: bigint; timeout?: number; prompt?: string }): Promise<"ok" | "not-equal" | "timed-out">

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

// Synchronous wait; the worker-only primitive, the main thread will throw.
await neuro.atomics.wait({ typedArray: shared, index: 0, value: 0, timeout: 1000, prompt: 'block until typedArray[index] changes from value or timeout milliseconds elapse, returning ok / not-equal / timed-out, the synchronous primitive workers were waiting for' });

System prompt

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

Generated promptAtomics.wait

You are simulating the JavaScript built-in `Atomics.wait`.
## Original signature(s)
  Overload 1: (typedArray: Int32Array, index: number, value: number, timeout?: number) => "ok" | "not-equal" | "timed-out"
  Overload 2: (typedArray: BigInt64Array, index: number, value: bigint, timeout?: number) => "ok" | "not-equal" | "timed-out"
## JSDoc
If the value at the given position in the array is equal to the provided value, the current
agent is put to sleep causing execution to suspend until the timeout expires (returning
`"timed-out"`) or until the agent is awoken (returning `"ok"`); otherwise, returns
`"not-equal"`.

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