Skip to main content

Account and Login

TARX supports two sign-in methods: Google OAuth (recommended) and email and password.


Signing Up

  1. Click Sign up on the TARX landing page.
  2. Click Continue with Google.
  3. Choose your Google account in the popup.
  4. TARX receives your Google profile (name, email, profile picture) and creates your account automatically.
  5. You're redirected to the Username Setup page — choose a unique handle (see Choosing Your Username below).

Google OAuth accounts do not require email verification — your Google account is already verified.

Option B: Email and Password

  1. Click Sign up.
  2. Enter your email address and choose a password (minimum 8 characters).
  3. Click Create Account.
  4. Check your inbox for a verification email from TARX.
  5. Click the verification link in the email.
  6. Return to TARX and sign in.
Verify your email

Email/password accounts must verify their email before they can access the full platform. If you don't see the verification email, check your spam folder. You can request a new verification email from the sign-in page.


Choosing Your Username

After your first sign-in (regardless of method), TARX prompts you to choose a username.

Your username is your public identity on the platform — it works like a GitHub handle:

  • Forms the base of all your resource URLs: /{username}/my-project/workflows
  • Must be 3–20 characters
  • Lowercase letters, numbers, and hyphens only (no spaces, no underscores)
  • Must be globally unique across all TARX users
  • Cannot be changed after setup

Choose something you're comfortable with being permanent. Common patterns:

  • Your first name: julian
  • Your handle from other platforms: julianros
  • Your company slug: acme-ai

Signing In

With Google

  1. Go to the TARX app.
  2. Click Sign in.
  3. Click Continue with Google.
  4. Select your account.

You're signed in immediately. No password needed.

With Email and Password

  1. Click Sign in.
  2. Enter your email and password.
  3. Click Sign in.

If your credentials are correct and your email is verified, you're taken to your projects dashboard.


Forgot Password

If you used email/password signup and forgot your password:

  1. Click Sign in.
  2. Click Forgot password? (below the password field).
  3. Enter your email address.
  4. Click Send reset link.
  5. Check your inbox for a password reset email from TARX.
  6. Click the link — you'll be taken to a page where you can set a new password.
  7. After resetting, sign in with your new password.
Password reset links expire after 1 hour for security.

Session Management

TARX sessions persist across browser tabs and page refreshes. You should rarely need to sign in again unless you explicitly sign out or clear browser storage.

Signing Out

  1. Click your avatar or profile picture in the top-right corner.
  2. Click Sign out.
  3. You're redirected to the sign-in page.
  4. All local session data is cleared.
Multiple accounts

If you need to use multiple TARX accounts (e.g., personal and work), use different browser profiles or incognito windows. Session data is scoped to the browser profile.


Account Security

Email/Password Accounts

  • TARX never stores passwords in plaintext — all credentials are securely hashed
  • Password reset links expire after 1 hour
  • Brute-force attempts are rate-limited at the API level

Google OAuth Accounts

  • TARX never stores your Google password
  • Access is governed by your Google account security settings
  • Revoke TARX's access at any time via Google Account permissions

API Key Security

Your LLM API keys (added in Settings → Keys & Secrets) are:

  • Encrypted at rest before storage
  • Never logged or transmitted in plaintext
  • Only decrypted in-memory at execution time on the backend
  • Not accessible via the API (you can see key names/IDs, not values)

How Authentication Works

TARX uses secure, industry-standard authentication. When you sign in via Google or email/password, your browser session is established automatically and all page navigation and API calls within the app are handled transparently. Passwords are never stored in plaintext, and sign-in is rate-limited against brute-force attempts.

For programmatic API access (scripts, CI/CD, external services), use a Platform API Key instead — see Settings → Keys & Secrets.


Troubleshooting

"Email not verified" error

Your email/password account needs verification. Check your spam folder for the verification email. On the sign-in page, click Resend verification email.

Google sign-in popup doesn't open

Check that your browser isn't blocking popups for the TARX domain. Safari users may need to allow popups in Safari Preferences → Websites → Pop-up Windows.

"Username already taken"

Usernames are globally unique. Try a variation — adding a number or a different separator: julian-2, julianros-dev, etc.

Signed out unexpectedly

Your browser session may have expired. Signing back in resolves it. If it happens repeatedly, check that your system clock is accurate (clock skew can cause session validation failures).