Allow offline validation before provider credentials are configured

Open
#9 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
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
cli, documentation, infrastructure, testing

Research direction

Start with the agents validate CLI flow and its contract tests, then compare how plan, apply, sessions, and deployments resolve credentials before network access. Done means a freshly generated project supports documented offline validation, distinguishes missing variables from schema or reference errors, preserves credential checks for other commands, and updates the English and Chinese getting-started docs.

Written by the indexing model from the issue text.

Description

enhancement

Problem

agents validate performs no provider API calls, but the generated agents.yaml contains ${VAR_NAME} references that currently must resolve before validation completes. A new user therefore cannot validate the generated project until real provider credentials exist.

Desired outcome

Provide a safe validation path that checks YAML structure, references, and provider capability rules without requiring secret values or contacting a provider. Planning and applying must continue to require resolved credentials.

Acceptance criteria

  • A freshly generated project can run the documented offline validation flow without real credentials.
  • Missing variables are still reported clearly, but are classified separately from schema or reference errors.
  • plan, apply, sessions, and deployments continue to fail before network access when required credentials are unresolved.
  • CLI contract tests cover both offline validation and credential-required commands.
  • English and Chinese getting-started docs describe the final behavior.
Dominant language
TypeScript
Stars
23
Forks
0
Avg merge
17h 56m
Merged PRs (30d)
12

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 modelstudioai/OpenAgentPack

All issues in modelstudioai/OpenAgentPack

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.