Repository navigation
Conversation
A saved login (session token, site and user ids, token name and secret, password and token file paths) applies only to the server and site it was made on. When --server names a different server (after normalising both URLs) or --site names a different site (compared case-insensitively, ignoring surrounding whitespace, with "default" meaning the default site), the saved login details are dropped and the command signs in from its own arguments, as it would with no saved session. Omitting --site keeps the saved site and its login. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Site names are case sensitive, so the site name is stored and sent as given and a case-only difference counts as a different site. As before, giving --server without --site uses the default site. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
A login saved by
tabcmd login(session token, site and user ids, token name and secret, password and token file paths) is now only used for the server and site it was made on.--servernames a different server (compared after normalising the URL), or--sitenames a different site (case-sensitive, surrounding whitespace ignored,defaultmeans the default site), the saved login is not used. The command signs in from its own arguments, as it would with no saved session.--serverand--site, or giving the saved values, keeps reusing the saved session as before.--serverwithout--siteselects the default site, as before.Behavior change
A saved login is no longer reused when
--servernames a different server or--sitenames a different site; the command then needs new credentials. Site names are compared case-sensitively, soSite-Aandsite-aare different sites, and the site name is stored and sent with the case given. As before,--serverwithout--siteuses the default site, anddefaultmeans the default site.A script that logged in once and then ran commands with a different
-sor--siteand no credentials now exits with "missing arguments / run 'tabcmd login -h'". Pass credentials on those commands, or runtabcmd loginagainst the new server or site first. Changing only the scheme (http vs https) counts as a different server.🤖 Generated with Claude Code