Skip to content

feat(kimi-code): use positional args and bare keywords for /connect#50

Merged
7Sageer merged 1 commit into
MoonshotAI:mainfrom
7Sageer:feature/connect-positional-args
May 26, 2026
Merged

feat(kimi-code): use positional args and bare keywords for /connect#50
7Sageer merged 1 commit into
MoonshotAI:mainfrom
7Sageer:feature/connect-positional-args

Conversation

@7Sageer

@7Sageer 7Sageer commented May 26, 2026

Copy link
Copy Markdown
Collaborator

Related Issue

Relates to #30 — follow-up to the /connect command introduced in that PR.

Problem

The /connect command currently uses CLI-style --flags (--url=..., --refresh) inside a slash-command context. This feels foreign compared to how peer agent CLIs handle slash-command arguments.

What changed

  • Replaced --url= with a positional URL argument: /connect https://example.com/catalog.json
  • Replaced --refresh with a bare keyword: /connect refresh
  • No-args invocation remains unchanged: /connect
  • Updated the built-in catalog hint from /connect --refresh to /connect refresh
  • Updated tests to cover the new syntax and reject the old --flag style

This aligns the parameter style with claude-code, pi, and opencode, where slash commands use positional args and bare keywords rather than --flags.

Checklist

  • I have read the CONTRIBUTING document.
  • I have linked a related issue, or explained the problem above.
  • I have added tests that prove my feature works.
  • This PR reuses the changeset from feat(kimi-code): add /connect command with bundled model catalog #30 (same release cycle, no new changeset needed).
  • This PR needs no doc update (minor parameter style change).

Replace the --flag style (/connect --url=..., /connect --refresh)
with positional arguments and bare keywords:

- /connect https://example.com/catalog.json
- /connect refresh
- /connect (no args, default behavior)

This aligns the slash-command UX with peer CLI tools (claude-code,
pi, opencode) where slash commands use bare words rather than
CLI-style flags.

Closes MoonshotAI#30 follow-up
@changeset-bot

changeset-bot Bot commented May 26, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 05b1041

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@7Sageer 7Sageer merged commit c473823 into MoonshotAI:main May 26, 2026
6 checks passed
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