Skip to content

support for standardized tool calling output #10

@gireeshm-vayavya

Description

@gireeshm-vayavya

Currently, nextCoder doesn't appear to support tool calling in a standardized format. When attempting to use the model for tool-use cases, the output is not structured in a way that is easily parsable for function execution. This makes it difficult to integrate nextCoder into existing agentic workflows and frameworks that rely on a predictable output format for tool calls.

I tried to use hermes protocol parser as qwen coder uses hermes and nextCoder is based on qwenCoder, but that didn't work.

I am trying to use nextcoder with vllm.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions