Skip to content

Where everything is — `contextcode conexion`

contextcode conexion is the command that answers “where is everything and how do I connect?”. It has three names — conexion, info, whoami — because nobody remembers which one each program chose.

Ventana de terminal
contextcode conexion # readable text
contextcode conexion --json # the same data as an object, for scripts
contextcode conexion --enlace # includes the URL WITH its token (the QR one)
contextcode conexion --qr # draws the link's QR in the terminal
“contextcode conexion”: version, folders, database and remote access status at a glance.
  • Version, executable and system — the key fact when you have two installations and think you’re using one while talking to the other.
  • Mode: escritorio + CLI, or solo CLI on a server with no graphical environment.
  • Configuration folder: ~/.context (or whatever CONTEXT_CONFIG_DIR says). That’s where providers, skills, hooks, MCP and remotos.json live.
  • Data folder: %LOCALAPPDATA%\ContextCodeDesktop on Windows, ~/.local/share/ContextCodeDesktop on Linux and ~/Library/Application Support/ContextCodeDesktop on macOS (or CONTEXT_DATA_DIR).
  • Database: context_code_desktop.db, encrypted with SQLCipher.
  • Backend log: logs/app.log, inside the data folder.
  • Console chats: where contextcode chat stores its conversations.
  • Remote access: whether there’s a link, on which port, how long it has left, whether the keychain returned its token, the local network URL, the stable tunnel one if there is any, and how many phones are paired.
  • Remote Context Codes configured from this machine.

Of the credentials it only says whether they exist. The URL with token appears only with --enlace or --qr, and you have to ask for it on purpose: the normal output is meant to be pasted into a support report without checking it line by line.

  • “I edited the configuration and nothing happens” — you probably edited the other installation’s. conexion tells you which one is active.
  • “The phone won’t connect” — look at the link status: it may have expired, or the keychain may not be returning the token (typical on a server, where the fix is serve --token-file).
  • “I want to open the database” — it gives you the exact path.
  • In a script — --json returns the same object without having to parse text.