Skip to content

Add s1 feedback command via the Agentback SDK - #12

Merged
fatwang2 merged 2 commits into
masterfrom
claude/agentback-feedback
Oct 26, 2026
Merged

fatwang2 merged 2 commits into
masterfrom
claude/agentback-feedback

Conversation

@fatwang2

Copy link
Copy Markdown
Member

Before: CLI users and the agents driving the CLI had no way to report problems with Search1API.

After: s1 feedback "what went wrong" sends a report to the Search1API team. It supports --category, --intent, --request-id, --model and --json, and - reads the message from stdin. When the user is logged in, the report is linked to their account. The welcome screen and README list the command.

How: runFeedbackCommand from the public agentback SDK (0.2.0) is mounted as a commander subcommand that passes its arguments through, using the project's write-only public key. Before sending, it calls the gateway's new GET /feedback/identity through fetchWithAuth, so API keys and OAuth (including refresh) both work, and attaches the signed account. If that lookup fails, the report is sent without an account.

Depends on fatwang2/search1api claude/agentback-sdk for GET /feedback/identity. Until that is deployed, reports still send, just without an account.

npm test passes on Node 22 and Node 18 (30 tests). The SDK declares Node >=20, which on Node 18 only produces an npm engine warning; the code paths the CLI uses run on 18.


Generated by Claude Code

Mounts agentback/cli's runFeedbackCommand as `s1 feedback`. Reports carry
the logged-in account signed by GET /feedback/identity when the lookup
succeeds.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V7jAP9YsE7D4HvphbaKNCc
@fatwang2 fatwang2 self-assigned this Oct 26, 2026
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V7jAP9YsE7D4HvphbaKNCc
@fatwang2
fatwang2 merged commit d45b3c5 into master Oct 26, 2026
2 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.

2 participants