Skip to content

docs: refresh recent behavior notes#262

Open
poe-code-agent[bot] wants to merge 4 commits intomainfrom
agent/update-documentation
Open

docs: refresh recent behavior notes#262
poe-code-agent[bot] wants to merge 4 commits intomainfrom
agent/update-documentation

Conversation

@poe-code-agent
Copy link
Copy Markdown
Contributor

@poe-code-agent poe-code-agent Bot commented Apr 29, 2026

Summary

  • Document Toolcraft group help child-command parameter tokens.
  • Document provider preferred-login resolution for OAuth-backed API-key login.
  • Document Goose spawn env overrides for file-backed credentials.
  • Document config inheritance self-discovery behavior from the latest config-extends and poe-code-config fixes.

Verification

  • Reviewed commits that landed on origin/main in the last 24 hours: 709c23ac and b48b4658.
  • Verified documentation claims against packages/config-extends/src/resolve.ts and packages/poe-code-config/src/store.ts.
  • Verified existing PR documentation claims against packages/providers/src/*, packages/agent-spawn/src/configs/goose.ts, and packages/toolcraft/README.md.
  • npx prettier --check packages/config-extends/README.md packages/poe-code-config/README.md
  • git diff --check

@poe-code-agent poe-code-agent Bot force-pushed the agent/update-documentation branch from 1846751 to 1717f39 Compare April 29, 2026 00:33
Copy link
Copy Markdown
Contributor Author

@poe-code-agent poe-code-agent Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Copy Markdown
Contributor Author

@poe-code-agent poe-code-agent Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@poe-code-agent poe-code-agent Bot force-pushed the agent/update-documentation branch from 1717f39 to 021fc50 Compare May 1, 2026 00:31
@poe-code-agent poe-code-agent Bot changed the title docs: document toolcraft group help parameters docs: refresh recent behavior notes May 1, 2026
Copy link
Copy Markdown
Contributor Author

@poe-code-agent poe-code-agent Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requested changes: one Toolcraft CLI help note contradicts current output.

Comment thread packages/toolcraft/README.md Outdated
@poe-code-agent poe-code-agent Bot force-pushed the agent/update-documentation branch from 021fc50 to 888fc84 Compare May 4, 2026 00:27
Copy link
Copy Markdown
Contributor Author

@poe-code-agent poe-code-agent Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requested changes: Toolcraft help docs still contradict positional rendering.

Comment thread packages/toolcraft/README.md Outdated

**Tree**: the `root` group is a `defineGroup` whose children are commands and sub-groups. Any depth. CLI flags, MCP tool names, and SDK methods are derived from the path.

**CLI help**: group help lists visible child commands with their parameter tokens inline. Required options appear as `--name <type>`, optional options and defaults appear in brackets like `[--limit <number>]`, and positional parameters stay unbracketed even when the underlying schema field is optional. Command-specific `--help` still shows the detailed parameter table.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This still contradicts the current formatter: formatHelpFieldFlags() uses formatPositionalToken() for positional fields, and formatPositionalToken() wraps optional/default positionals in brackets (for example [agent]).

Suggested change
**CLI help**: group help lists visible child commands with their parameter tokens inline. Required options appear as `--name <type>`, optional options and defaults appear in brackets like `[--limit <number>]`, and positional parameters stay unbracketed even when the underlying schema field is optional. Command-specific `--help` still shows the detailed parameter table.
**CLI help**: group help lists visible child commands with their parameter tokens inline. Required options appear as `--name <type>`, optional options and defaults appear in brackets like `[--limit <number>]`, and positional parameters render as `<name>` or `[name]` depending on whether the underlying schema field is required. Command-specific `--help` still shows the detailed parameter table.

Co-authored-by: poe-code-agent[bot] <254571472+poe-code-agent[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant