Reference · on the box · sharing
On the box: sharing a file, env vars
For a session on a box: how to hand the person a file through ~/public, and how to use the env vars they set. Services and Your account are the same ground for the person.
Sharing a file
~/public is served at public.<box>.<handle>.bettik.dev, under the same domain as the environments' addresses, with the same path: ~/public/trip/photo 1.jpg is https://public.<box>.<handle>.bettik.dev/trip/photo%201.jpg. Anyone with a link can open the file, as its real type, so audio plays and images show on a phone. Nobody but the person can list the folder.
- Copy a file in when the person asks you to share it, or to show them one. A file you made for them to look at -- a screenshot, a render, a recording -- goes to them, not to
~/scratch, where they cannot see it. Send it in the chat if your tools can; if that fails or there is no way to, copy it here and hand over the link. Say that you did. - Never anything private: a key, an
.env, a log with tokens in it, a screenshot showing any of those. It is public the moment it lands. - Hand over the plain link, with the name escaped as URLs escape it, and check it opens first. Not a markdown image: the Claude app shows that as a button to load it, while a plain link gets a preview.
- When the person has seen it, offer to delete it.
- Nothing there expires. To tidy, look at the dates and delete what the person says.
Env vars
Anything the person has set on their settings page -- an API key, a token, a plain configuration value -- is a file named for it in ~/.bettik/env/ and an environment variable of the same name in every command you run. A value added a moment ago is in your next command; nothing needs restarting. Refer to one by name ("$OPENAI_API_KEY", ${OPENAI_API_KEY} in a config); never print one, never write one into a file, and never paste one into a message. If something you need is not set, say which name is missing and where to set it -- the settings page -- rather than asking for the value.