Skip to content

fix: register-agent matches new /agents/register spec (replay of pr38)#1

Open
antfleet-ops wants to merge 1 commit into
mainfrom
replay/pr38-register-agent
Open

fix: register-agent matches new /agents/register spec (replay of pr38)#1
antfleet-ops wants to merge 1 commit into
mainfrom
replay/pr38-register-agent

Conversation

@antfleet-ops
Copy link
Copy Markdown
Contributor

Replay of Reppo-Labs/reppo-cli#38 — agent registration API spec fix (auth/registration surface).

@antfleet
Copy link
Copy Markdown

antfleet Bot commented May 25, 2026

AntFleet · 1 finding

Both reviewers flagged the items below on the changed files. AntFleet posts only what two independent frontier models agree on.


Docs-gap · Medium — README Authentication table incorrectly claims REPPO_API_KEY is required for register-agent (command uses no auth)
README.md:25-26

The README states REPPO_API_KEY is required for register-agent, but the implementation calls a no-auth endpoint and does not read or send any API key. This inconsistency will confuse users and scripts about necessary environment setup.

Fix: Update the Authentication table to remove REPPO_API_KEY as a requirement for register-agent. Clarify that register-agent is unauthenticated and returns the persistent apiKey used for subsequent agent-scoped endpoints. Also note that agent-scoped endpoints use that returned apiKey as Bearer auth.

Proposed patch (model: claude-opus-4-7)
| register-agent | None (public endpoint; returns a persistent `apiKey`) |
| (others)       | Bearer `apiKey` returned from register-agent |

Note: `register-agent` is unauthenticated. Save the `apiKey` it returns and pass it as a Bearer token for all subsequent agent-scoped endpoints.

Review 44a066f2 · claude-opus-4-7 + gpt-5 (unanimous) · 131s · ~$0.40

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