This repository was archived by the owner on Oct 13, 2026. It is now read-only.
Repository navigation
Conversation
Settings (window, web, both phones) gets an API keys section: Add API key (a name and the key; the key is typed as dots and never shown again), View API keys (the names, each with Delete). Keys live in one .env file, <home>/secrets/api.env (0600 in a 0700 folder), a NAME='value' line each so a shell can load it; names become environment variables (openai key -> OPENAI_KEY). Agents get an <api_keys> block with the names and the path, told to load the file in the same command that needs a key and never to print, read, log or write a value; they can list current names with sed. No client, reply, screen or prompt carries a value. The phones' Settings rows can carry fields now, and Android's Settings list clears the navigation bar (its last row was under it). Laws keys_*; test/apikeys_test.bend. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
jlcjak
marked this pull request as draft
September 30, 2026 21:31
Contributor
Author
|
Moved to BackplaneWorks/Backplane#29 (merged). |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Settings on the window, web and both phones gets an API keys section:
Keys live in one
.envfile,<home>/secrets/api.env(0600, in a 0700 folder), oneNAME='value'line each so a shell can load it. Names become environment variables (openai key→OPENAI_KEY); a service needing two keys gets two names.Agents get an
<api_keys>block with the names and the path. It tells them to load the file in the same command that needs a key (set -a; . FILE; set +a; curl -H "Authorization: Bearer $NAME" …), and never to print, read, log or write a value. They can list current names withsed. No client, RPC reply, phone screen, phone saved state or prompt carries a value.Also: the phones' Settings rows can carry input fields, and Android's Settings list now clears the navigation bar (its last row sat under it).
Tested:
scripts/check.sh(lawskeys_*),scripts/test.sh,test/apikeys_test.bend',$,\,"and a backtick loads back unchanged throughshandbashclauderecording its arguments: names in the prompt, no values, file modes🤖 Generated with Claude Code