Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Constrained tool-call decoding: validate (local vLLM) + wire

Open
#868 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
ai, backend

Research direction

Review provider/constrained.ts and its unit tests on branch feat/constrained-decoding, then inspect session/llm.ts for the marker-wrapped, flag-gated local-provider path. Run the local vLLM constrained-ON/OFF A/B on a tool-heavy task set; done means measurable parse-rate improvement or fewer malformed calls without quality loss, followed by wiring the validated block.

Written by the indexing model from the issue text.

Description

Context

provider/constrained.ts (grammar/JSON-Schema constrained decoding for local providers) was split out of #858 so the validated tool-retrieval lever could land clean. Code + unit tests live on branch feat/constrained-decoding.

Work
  1. Validate: run a local vLLM guided-decoding A/B (constrained ON vs OFF) on a tool-heavy task set; confirm it improves tool-call parse-rate / reduces malformed calls at no quality cost.
  2. Wire: re-add the flag-gated (ALTIMATE_CONSTRAINED_TOOLCALLS, local-providers-only, toolChoice: "required") block into session/llm.ts (marker-wrapped).
  3. Open the PR once it actually does something measurable.

Do NOT open a PR with the flag wired-but-unvalidated or present-but-unwired (the no-op-flag anti-pattern). Branch: feat/constrained-decoding.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 3h
Merged PRs (30d)
65

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.