Skip to content

feat: tag openclaw harness on signup + plugin-setup skill - #20

Merged
dimavrem22 merged 9 commits into
mainfrom
feat/agent-signup-harness
Jun 26, 2026
Merged

feat: tag openclaw harness on signup + plugin-setup skill#20
dimavrem22 merged 9 commits into
mainfrom
feat/agent-signup-harness

Conversation

@dimavrem22

@dimavrem22 dimavrem22 commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add harness: "openclaw" to the Inkbox.signup(...) request in src/setup-wizard.ts so self-signups driven by this harness are attributed correctly.
  • Add a slim agent-facing skill skills/inkbox-plugin-setup/SKILL.md that tells the agent: if it self-signed up to Inkbox but the plugin is not configured, ask the human for explicit permission before enabling the plugin, since doing so wires native messaging channels into its runtime.

Dependency

The harness field is an optional, forward-compatible addition. This depends on the Inkbox SDK gaining the harness field on the signup request (coordinated PR). It is harmless until then.

Related PRs (agent-signup harness)

@dimavrem22

Copy link
Copy Markdown
Contributor Author

codex: This currently fails the PR check at src/setup-wizard.ts:1062: package-lock.json still resolves @inkbox/sdk to 0.4.7, whose AgentSignupRequest type does not include harness, so tsc reports TS2353. Please bump @inkbox/sdk/the lockfile to the SDK release that includes the harness field (the SDK PR shows 0.4.9) and update the setup-wizard test expectation to include harness: "openclaw" in the Inkbox.signup call.

@dimavrem22

Copy link
Copy Markdown
Contributor Author

Source-level fixes in cbadbb6: bumped @inkbox/sdk ^0.4.7^0.4.9 and added harness: "openclaw" to the setup-wizard signup test expectation. I intentionally left package-lock.json untouched — @inkbox/sdk@0.4.9 (the release that adds the harness field) ships with the SDK PR and is not on npm yet, so regenerating the lockfile would fail to resolve it. The lockfile bump + tsc green will land once the SDK publishes; this PR is part of that coordinated set.

@dimavrem22

Copy link
Copy Markdown
Contributor Author

Correction: the harness-capable SDK release is 0.4.10, not 0.4.9. @inkbox/sdk pin is now ^0.4.10 (fcff184). Lockfile still regenerates at publish, once @inkbox/sdk@0.4.10 is on npm.

@dimavrem22
dimavrem22 marked this pull request as ready for review June 26, 2026 20:15
dimavrem22 and others added 9 commits June 26, 2026 21:15
Add `harness: "openclaw"` to the Inkbox.signup request so self-signups
are attributed to this harness, and add a slim agent-facing skill that
gates Inkbox plugin setup on explicit human permission.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The setup wizard passes harness: "openclaw" to Inkbox.signup, which
requires the AgentSignupRequest harness field added in SDK 0.4.9. Bump
the dependency range and update the signup test expectation to include
the harness arg.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0.4.10 is the release that introduces the agent-signup harness param;
0.4.9 was an earlier release that predates it. Lockfile left untouched
since 0.4.10 is not yet published to npm.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…lugin setup

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ermission

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The plugin's setup wizard already configures the plugin during signup, so a
separate agent-facing "ask permission, then set it up yourself" instruction is
redundant. Drop it; keep the harness= signup tagging.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…0.4.10

The typing refresh interval is now 40s (IMESSAGE_TYPING_REFRESH_MS), but the
createIMessageTypingPulse tests still assumed the old 2s cadence (expecting a
pulse after 2s and 150 pulses at the cap). Export the refresh/cap constants and
derive the expectations from them so the tests track the real interval (1
immediate + one per 40s tick until the 300s cap = 8) and can't desync again.

Also sync package-lock to @inkbox/sdk 0.4.10 — package.json was bumped to
^0.4.10 but the lockfile still pinned 0.4.7, which broke `npm ci`.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@dimavrem22
dimavrem22 force-pushed the feat/agent-signup-harness branch from 5a45061 to 53f810f Compare June 26, 2026 21:22
@dimavrem22
dimavrem22 merged commit 8bd294a into main Jun 26, 2026
1 check passed
@dimavrem22
dimavrem22 deleted the feat/agent-signup-harness branch June 26, 2026 21:25
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