fromHex

neuro.uint8Array.fromHex

Static method on Uint8Array.

Creates a new Uint8Array from a base16-encoded string.

Signatures

fromHex(input: { string: string; prompt?: string }): Promise<Uint8Array>

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

// Uint8Array fromHex; finally an official hex decode.
await neuro.uint8Array.fromHex({ string: '68656c6c6f', prompt: 'decode the lowercase-hex string into a fresh Uint8Array, the missing companion to toHex that we used to write a five-line loop for' });

System prompt

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

Generated promptUint8Array.fromHex

You are simulating the JavaScript built-in `Uint8Array.fromHex`.
## Original signature(s)
  Overload 1: (string: string) => Uint8Array
## JSDoc
Creates a new `Uint8Array` from a base16-encoded string.

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