@voltagent/[email protected]

Patch Changes

• #102 cdfec65 Thanks @omeraplak! - refactor: use 'instructions' field for Agent definitions in examples - #88

  Updated documentation examples (READMEs, docs, blogs) and relevant package code examples to use the instructions field instead of description when defining Agent instances.

  This change aligns the examples with the preferred API usage for the Agent class, where instructions provides behavioral guidance to the agent/LLM. This prepares for the eventual deprecation of the description field specifically for Agent class definitions.

  Example Change for Agent Definition:

    const agent = new Agent({
      name: "My Assistant",
  -   description: "A helpful assistant.",
  +   instructions: "A helpful assistant.",
      llm: new VercelAIProvider(),
      model: openai("gpt-4o-mini"),
    });

• Updated dependencies [cdfec65]:

  • @voltagent/[email protected]

@voltagent/[email protected]

Patch Changes

• #102 cdfec65 Thanks @omeraplak! - refactor: use 'instructions' field for Agent definitions in examples - #88

  Updated documentation examples (READMEs, docs, blogs) and relevant package code examples to use the instructions field instead of description when defining Agent instances.

  This change aligns the examples with the preferred API usage for the Agent class, where instructions provides behavioral guidance to the agent/LLM. This prepares for the eventual deprecation of the description field specifically for Agent class definitions.

  Example Change for Agent Definition:

    const agent = new Agent({
      name: "My Assistant",
  -   description: "A helpful assistant.",
  +   instructions: "A helpful assistant.",
      llm: new VercelAIProvider(),
      model: openai("gpt-4o-mini"),
    });

• Updated dependencies [cdfec65]:

  • @voltagent/[email protected]

@voltagent/[email protected]

Patch Changes

• #102 cdfec65 Thanks @omeraplak! - refactor: use 'instructions' field for Agent definitions in examples - #88

  Updated documentation examples (READMEs, docs, blogs) and relevant package code examples to use the instructions field instead of description when defining Agent instances.

  This change aligns the examples with the preferred API usage for the Agent class, where instructions provides behavioral guidance to the agent/LLM. This prepares for the eventual deprecation of the description field specifically for Agent class definitions.

  Example Change for Agent Definition:

    const agent = new Agent({
      name: "My Assistant",
  -   description: "A helpful assistant.",
  +   instructions: "A helpful assistant.",
      llm: new VercelAIProvider(),
      model: openai("gpt-4o-mini"),
    });

• Updated dependencies [cdfec65]:

  • @voltagent/[email protected]

@voltagent/[email protected]

Patch Changes

• #102 cdfec65 Thanks @omeraplak! - refactor: use 'instructions' field for Agent definitions in examples - #88

  Updated documentation examples (READMEs, docs, blogs) and relevant package code examples to use the instructions field instead of description when defining Agent instances.

  This change aligns the examples with the preferred API usage for the Agent class, where instructions provides behavioral guidance to the agent/LLM. This prepares for the eventual deprecation of the description field specifically for Agent class definitions.

  Example Change for Agent Definition:

    const agent = new Agent({
      name: "My Assistant",
  -   description: "A helpful assistant.",
  +   instructions: "A helpful assistant.",
      llm: new VercelAIProvider(),
      model: openai("gpt-4o-mini"),
    });

• Updated dependencies [cdfec65]:

  • @voltagent/[email protected]

@voltagent/[email protected]

Patch Changes

• #102 cdfec65 Thanks @omeraplak! - refactor: use 'instructions' field for Agent definitions in examples - #88

  Updated documentation examples (READMEs, docs, blogs) and relevant package code examples to use the instructions field instead of description when defining Agent instances.

  This change aligns the examples with the preferred API usage for the Agent class, where instructions provides behavioral guidance to the agent/LLM. This prepares for the eventual deprecation of the description field specifically for Agent class definitions.

  Example Change for Agent Definition:

    const agent = new Agent({
      name: "My Assistant",
  -   description: "A helpful assistant.",
  +   instructions: "A helpful assistant.",
      llm: new VercelAIProvider(),
      model: openai("gpt-4o-mini"),
    });

@voltagent/[email protected]

Patch Changes

• #102 cdfec65 Thanks @omeraplak! - refactor: use 'instructions' field for Agent definitions in examples - #88

  Updated documentation examples (READMEs, docs, blogs) and relevant package code examples to use the instructions field instead of description when defining Agent instances.

  This change aligns the examples with the preferred API usage for the Agent class, where instructions provides behavioral guidance to the agent/LLM. This prepares for the eventual deprecation of the description field specifically for Agent class definitions.

  Example Change for Agent Definition:

    const agent = new Agent({
      name: "My Assistant",
  -   description: "A helpful assistant.",
  +   instructions: "A helpful assistant.",
      llm: new VercelAIProvider(),
      model: openai("gpt-4o-mini"),
    });

@voltagent/[email protected]

Patch Changes

• Updated dependencies [cdfec65]:
  • @voltagent/[email protected]

[email protected]

Patch Changes

• 13db262 Thanks @omeraplak! - fix: Update Zod to version 3.24.2 to resolve "Type instantiation is excessively deep and possibly infinite" error (related to colinhacks/zod#3435).

@voltagent/[email protected]

Patch Changes

• 13db262 Thanks @omeraplak! - fix: Update Zod to version 3.24.2 to resolve "Type instantiation is excessively deep and possibly infinite" error (related to colinhacks/zod#3435).

• Updated dependencies [f7de864, 13db262]:

  • @voltagent/[email protected]
  • @voltagent/[email protected]

@voltagent/[email protected]

Patch Changes

• #98 c3db06d Thanks @yusuf-eren! - feat(xsAI): add xsAI voice provider

  This adds support for the xsAI voice provider, including:

  • Core provider implementation support
  • Support for API key authentication and custom headers
  • Base URL configuration for API endpoints

• Updated dependencies [f7de864, 13db262]:

  • @voltagent/[email protected]