Skip to main content

Module account

Module account 

Source
Expand description

The part of a login that lives inside a harness’s shared settings file rather than in a file of its own.

Claude Code keeps its tokens in ~/.claude/.credentials.json, but the other half of a sign-in in ~/.claude.json, beside the folders it trusts and the servers it starts: the account (oauthAccount) and the end of its first-start questions (hasCompletedOnboarding), which a sign-in is one of. Read in its 2.1.282 bundle: the first start is shown whenever that flag is missing, and it always holds the step that signs in, whatever tokens are on disk. A home given the tokens alone was therefore asked to sign in again on a profile whose image writes no ~/.claude.json, and everywhere else showed no account.

The file cannot be copied whole: in a workspace it holds what the profile’s template wrote and what QCode’s bridge registered, and the login container’s copy holds neither. So the keys of the login are taken out on their own, into MERGE_DIR of the profile’s credentials volume, and merged into the home’s file when a home is given the login: every key the home has stays, the login’s keys are the profile’s.

Structs§

Shared
A settings file of a harness that a login writes some of its keys into.

Constants§

MERGE_DIR
The folder of a credentials volume, and of a capture, that holds the keys to be merged into a home’s files rather than copied over them: the same path under it as the file under the home.

Functions§

merge
The command, run in the container that gives a home its profile’s login after the store was copied in, that merges the login’s keys into the home’s shared files.
shared
The file harness’s login shares with its other settings, if it has one.
strip
The command, run in a profile’s shell before what it holds becomes the profile’s image, that takes the login’s keys out of harness’s shared file: a login never goes into an image, where every workspace of the profile would carry it; None for a harness whose login is only files of its own.
take
The command, run in the container a login was made in, that takes the login’s keys of harness’s shared file out into the capture folder capture; None for a harness whose login is only files of its own.