openclaw - 💡(How to fix) Fix ClawHub CLI missing license acceptance flag for publish command [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#43774Fetched 2026-04-08 00:18:12
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
cross-referenced ×1

The ClawHub CLI (v0.7.0) is missing a flag to accept license terms when publishing skills. Users attempting to publish a skill receive an error:

acceptLicenseTerms: invalid value

This blocks skill publication entirely from the CLI.

Error Message

The ClawHub CLI (v0.7.0) is missing a flag to accept license terms when publishing skills. Users attempting to publish a skill receive an error: 3. Observe the error about acceptLicenseTerms: invalid value

Root Cause

The ClawHub CLI (v0.7.0) is missing a flag to accept license terms when publishing skills. Users attempting to publish a skill receive an error:

acceptLicenseTerms: invalid value

This blocks skill publication entirely from the CLI.

Fix Action

Workaround

Currently, users must:

  1. Visit https://clawhub.com
  2. Accept the license terms via the website UI
  3. Then CLI publish commands will work

Code Example

acceptLicenseTerms: invalid value

---

clawhub publish ./my-skill --accept-license

---

Publishing skill requires accepting license terms.
Do you accept the license terms? [y/N]
RAW_BUFFERClick to expand / collapse

Description

The ClawHub CLI (v0.7.0) is missing a flag to accept license terms when publishing skills. Users attempting to publish a skill receive an error:

acceptLicenseTerms: invalid value

This blocks skill publication entirely from the CLI.

Reproduction Steps

  1. Install ClawHub CLI v0.7.0
  2. Attempt to publish a skill: clawhub publish ./my-skill
  3. Observe the error about acceptLicenseTerms: invalid value

Expected Behavior

The CLI should include a flag like --accept-license or --accept-terms to allow users to accept license terms as part of the publish command.

Workaround

Currently, users must:

  1. Visit https://clawhub.com
  2. Accept the license terms via the website UI
  3. Then CLI publish commands will work

Suggested Fix

Add a flag to the publish command:

clawhub publish ./my-skill --accept-license

Or prompt interactively:

Publishing skill requires accepting license terms.
Do you accept the license terms? [y/N]

Environment

  • ClawHub CLI: v0.7.0
  • Node: v25.6.1
  • OS: Linux (Debian)

Related

This affects users trying to publish skills from the command line without first visiting the website.

extent analysis

Problem Summary

The publish command of the ClawHub CLI (v0.7.0) rejects requests because it never receives the required acceptLicenseTerms flag/value. Users must manually accept the license on the website before the CLI will succeed.

Root Cause

  • The CLI’s publish command does not expose a way to set acceptLicenseTerms.
  • The underlying API expects a boolean acceptLicenseTerms field; when the CLI omits it, the server returns “invalid value”.
  • No interactive prompt is present, so the CLI fails immediately.

Fix Plan

Below is a concrete, step‑by‑step plan to add a --accept-license flag (and an interactive fallback) to the publish command.

1. Update the command definition

Assuming the CLI uses commander (most common for Node CLIs). Add a boolean option.

// src/commands/publish.ts
import { Command } from 'commander';
import inquirer from 'inquirer';
import { publishSkill } from '../services/publish';

export function registerPublish(program: Command) {
  program
    .command('publish <path>')
    .description('Publish a skill to ClawHub')
    .option('-a, --accept-license', 'Accept the license terms for this publish')
    .action(async (path: string, opts: { acceptLicense?: boolean }) => {
      // 1️⃣ Resolve acceptance
      const accept = await resolveLicenseAcceptance(opts.acceptLicense);
      // 2️⃣ Call the service with the flag
      await publishSkill({ path, acceptLicenseTerms: accept });
    });
}

/**
 * Returns true if the user has accepted the license.
 * - If the flag is supplied → true.
 * - If not, ask interactively.
 */
async function resolveLicenseAcceptance(flag?: boolean): Promise<boolean> {
  if (flag) return true;

  const { answer } = await inquirer.prompt([
    {
      type: 'confirm',
      name: 'answer',
      message:
        'Publishing this skill requires accepting the ClawHub license terms. Do you accept?',
      default: false,
    },
  ]);

  if (!answer) {
    console.error('❌ License terms not accepted – aborting publish.');
    process.exit(1);
  }
  return true;
}

2. Propagate the flag to

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix ClawHub CLI missing license acceptance flag for publish command [1 participants]