Repository navigation
product: HANZO_API_KEY is a machine caller's bearer - #47
Merged
Merged
Conversation
A caller that holds only an API key could not use any cloud command: a key is never filed as an identity, so a sandbox leased with a key said `not signed in`, and one signed in as a person read none of the sessions the key had opened (404: a session belongs to its actor). Read HANZO_API_KEY at the point of use in Seam::open, ahead of the stored login, as `hanzo dev`'s provider already does. Claude-Session: https://claude.ai/code/session_015XYKLnBbrbajqj1GpRydF8
The deployed document dropped PUT /v1/ai/limits, so the client lane read the committed projection as stale. Claude-Session: https://claude.ai/code/session_015XYKLnBbrbajqj1GpRydF8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Seam::openreadsHANZO_API_KEYat the point of use, ahead of the stored login (ashanzo dev's provider does). A key is still never filed as an identity.Why: the Grok bot's sessions belong to actor
hanzo/hanzo/z(its org keyhanzo/grok-bot-iam). In a box leased with that key the CLI has no session (not signed in); signed in as anyone else it gets404 session not found. With the key in the environment the lookup answers 200.Tests:
cargo test --bin hanzo401 passed (newa_machine_key_is_the_variable_trimmed_and_nothing_when_blank),cargo clippy --bin hanzoclean,make verifyno drift.https://claude.ai/code/session_015XYKLnBbrbajqj1GpRydF8