Account and activation

When access is available, subscribe, sign in, activate a device and recover account access.

Linux AMD64, Linux ARM64, Windows x64 · Release 0.1.5

On this page

Choose the right next step

New company access starts with a scoped quote, not a platform picker or automatic checkout. Compare the published company plans, then discuss your deployment. Your agreement defines named users, concurrent work, supported installations and the monthly AI allowance. A quote request does not charge a card, start a subscription or activate AI. Existing customer contracts keep their agreed prices and limits.

You can evaluate the local editor without buying a plan: check compatibility, download the supported application and follow the first-project tutorial. The company evaluation guide brings platform, workflow, data and recovery information together. Do not send confidential files with an initial enquiry.

Invited employee? Use the sign-in email your administrator invited. You do not need to purchase another subscription or verify your employer’s billing email. A TraceForge agreement and an OpenAI BYOK bill are separate.

Sign in with email and password

Open Your account. Use Create an account, enter your email and a password of 12–256 characters, then verify the private code sent to that address. Creating an identity grants no paid entitlement. After verification, sign in with your email and password.

Forgot your password? Choose that option on the sign-in form, request a code, and enter it with a new password. Verification and recovery codes expire after one hour and work once. A successful password reset signs out existing identity sessions; it does not remove connected providers, cancel a subscription or delete project files. An existing Google/GitHub user can establish an email password only by proving access to that account’s email through recovery—not by registering a matching email alone.

Check your inbox and spam folder. If a request times out, check for its email before sending again; TraceForge does not silently retry the browser action. Never paste private codes into a URL, support request or the Agent. Billing-email codes are a separate form and do not work here.

Sign in with Google or GitHub

Open Your account and choose Continue with Google or Continue with GitHub. Finish the provider's sign-in and return to TraceForge. Your identity section shows the connected provider. You can connect the other provider from that same section; a matching email address alone never links accounts.

Signing in identifies you. It does not purchase a subscription, activate a desktop or grant billing access. Do not enter provider passwords into TraceForge, support or the Agent.

Join or administer a company workspace

After signing in, open Company workspace. Choose the workspace you intend to use; your role and subscription state appear below its name. A newly created identity without paid access shows evaluation, quote and invitation steps—not an account failure.

  • Join: open Accept a company invitation and enter the private code supplied by your administrator. Sign in using the invited, verified email. The code expires after one hour and can be accepted once. If your provider uses a different email, ask the administrator to invite the email shown under Your identity; do not share provider credentials or link accounts by email alone.
  • Invite: an owner or administrator with active agreed access can select Create invitation code. Share the code directly with the named colleague through your existing secure channel. This action sends no email. The code is shown only in the current page and cleared when you leave or hide it. Acceptance checks the inviter’s current authority and available seats.
  • Roles and removal: owners can save role changes or remove a colleague after confirmation. Administrators can invite members; only owners can invite administrators or change roles. The last owner cannot be removed or demoted. Removing membership does not delete local project files; it is not a remote wipe or a revocation of unrelated billing access.
  • Shared usage: members can see their workspace’s server-reported allowance. New company agreements use USD; existing credit agreements keep their original units and limits. Pending usage holds are separate from completed usage. No automatic overage is enabled. If usage cannot be loaded, the page says so instead of inventing a balance.

Signing in or accepting an invitation does not by itself start paid AI, activate a desktop, authorize billing changes or approve engineering Apply. If a workspace or seat is missing, contact its owner before buying anything. A separately verified billing contact may be different from the workspace owner.

Verify billing access

  1. Open Your account.
  2. Under Access & usage, open Verify billing email. Enter the billing email and select Email a code.
  3. Open the newest message, copy its private code and enter it under Already have a code?
  4. Select Verify code. Access & usage shows subscriptions and balances; Devices & sessions shows desktop installations available to that verified email.

Expected result: billing details replace the verification forms. Billing uses a separate protected browser session, even if you already signed in with Google or GitHub. It does not need an OpenAI API key. Sign-in codes expire after 15 minutes. Request another code if yours expired. Never post the code to support, a URL or the Agent.

Activate the desktop application

Website sign-in codes and desktop activation codes are different. Open the activation page to request activation instructions for the billing email. In TraceForge, open the native account/access dialog and enter the desktop activation code from that message. Enter it only in the application, not into the Agent composer.

Confirm the application reports the expected account and subscription. If a device limit is reached, sign in to the website and inspect the registered devices before revoking one you own. Do not revoke a device used by someone else just to make room.

Recover missing access

  • No email: check spelling, spam and the billing address on your agreement or original purchase. Wait before requesting another message; sending repeatedly can trigger rate limits.
  • Payment succeeded, access pending: refresh account status. If it remains pending, use billing support with your billing email and approximate purchase time. Do not share payment-card details.
  • Code rejected: check whether it is a website code or a desktop code, then request the correct replacement.
  • Cancelled subscription: use the offered recovery/reactivation path rather than creating an unrelated subscription. It preserves the existing contract where supported.
  • Service unavailable: keep the error message and try again later. Reinstalling generally does not fix a remote account outage.

Billing and signing out

Manage billing opens Stripe's email-verified customer portal. It may verify your billing email again; desktop activation is not authority to administer billing. Use it for invoices, payment methods and supported subscription changes.

On a shared browser, select Sign out of this browser when finished. It ends this browser's identity and billing sessions; it does not sign out other browsers, cancel a subscription or erase project files. If either service cannot confirm sign-out, private details are hidden and the page tells you which part needs a retry. Browser sessions and activated desktops are listed separately. See usage and billing for renewal, cancellation and exhaustion behavior.

Search documentation

Type to search the TraceForge guides.