Account and Sync Help

Use this guide when the Pitchblend account control or Memory Sync needs
attention. Start with the message you can see; do not delete app data,
credential files, or sync journals as a first troubleshooting step.

The workspace does not open

Geist couldn’t start

Pitchblend could not start or reach its local Geist runtime. Read the detail
under the heading, then select Retry startup once.

In an installed app, reinstall if the detail says a bundled runtime or runtime
manifest is missing. In a source checkout, follow the command printed in the
detail; Windows and Linux need both staged CPU and Vulkan llama.cpp runtimes.

Workspace is stopped

The managed runtime exited or the configured attach-mode server is not
reachable. Select Retry startup in normal managed mode. In attach mode,
start the external Geist server at the configured GEIST_URL instead; the
desktop app cannot start that process for you.

Required UI couldn’t load

The account or Memory Sync control did not mount in the current Geist page.
Select Retry startup to reload the embedded workspace. If it happens again,
restart Pitchblend. Reinstall the packaged app if the error persists; do not
try to download or replace an individual plugin.

On a first-launch plugin failure, Pitchblend may instead show a native dialog
titled Pitchblend failed to start and close. Reinstall the complete app from
the trusted distribution source.

Pitchblend couldn’t start

If the detail says The startup shell failed to load. Please reinstall
PitchblendAI., reinstall the complete app. This error has no in-app retry
because the recovery controls themselves did not load.

The account button says sign-in is unavailable

• Wait if its tooltip says Pitchblend account is loading.
• In a normal packaged app, restart Pitchblend and check that you can reach the
  Pitchblend identity service in your browser.
• In a source build, Identity is disabled by default. Use the explicit source
  configuration in
  Developer Mode.
• Do not try to redirect an installed app with environment variables. Packaged
  clients use the built-in Pitchblend authority.

If the account bridge itself failed, the startup gate should prevent the
workspace from opening. Treat that as Required UI couldn’t load rather than
an account-password problem.

The browser sign-in is stuck

1. Return to Pitchblend and select Cancel.
2. Wait for Cancelling... to finish.
3. Select Sign in and try again.

The browser must be able to return to a temporary 127.0.0.1 address. Local
security software that blocks loopback callbacks can prevent completion.

If the browser says Pitchblend sign-in was not completed., begin again from
the desktop app. Messages such as Invalid sign-in state, Invalid identity
issuer, or Invalid identity response mean Pitchblend rejected an unsafe
or stale callback. Do not work around those checks.

Sign-in or session refresh failed

The account control intentionally shows a short, safe error. Common forms say
that the identity service timed out, returned an HTTP error, rejected the
session, failed security validation, or that you should try again.

• Check your Internet connection and system clock.
• Retry Sign in once.
• If a previously signed-in account is still shown, Pitchblend may be retaining
  its last safe summary while it retries a temporary refresh failure.
• If the issue persists, sign out and sign in again.

Never send an authorization code, access token, refresh token, or raw license
key to someone who asks for it as part of troubleshooting.

Retry sign out appears

Pitchblend could not prove that saved local credentials were removed. Select
Retry sign out and wait for Retrying....

If it fails again, close Pitchblend, restart the operating system, and retry.
Contact Pitchblend Support before manually changing the operating system's
credential store. Pitchblend quarantines this failed session so it is not
silently restored on the next launch.

No active or eligible license appears

The account menu shows No active license when the identity service did not
return an active license. Memory Sync may also disable a license that is active
but does not meet sync eligibility or has no available device seat.

Try these checks:

1. Confirm you signed in with the account that owns the license.
2. Close and reopen the account menu after the account refresh completes.
3. Open Memory Sync and read the device count beside each license.
4. Confirm the license or linked subscription is still active and has a sync
   device allowance.

Signing out does not delete the license. License and subscription changes are
made through the Pitchblend account/service, not by editing desktop files.

Memory Sync status guide

Off

Turn on Sync Geist memories if you want to sync. Leaving it off is safe and
does not affect local Geist memories.

Setup needed

Choose an eligible license, then select Bootstrap first device only for the
first device. Otherwise enter a Pairing code from an enrolled device and
select Join existing devices.

Connecting or Syncing

Usually no action is needed. Keep both devices awake and connected. If the
state becomes Needs attention, open the panel and read its error notice.

Needs attention

The panel explains the specific problem. Common notices are covered below. A
transport failure may clear automatically when the direct or LAN connection
recovers.

Suspended

The license has fewer available seats than enrolled devices. Local memories
remain unchanged. Restore the license's device allowance or revoke an unused
device from an active enrolled device.

Removed

This device was revoked from the old sync group. Local memories remain
unchanged. Choose another eligible license, or switch and enroll again if that
is intentional.

Memory Sync is unavailable

Match the notice in the panel:

• Sign in with Pitchblend Identity before configuring device sync. — sign
  in with the account control first.
• Memory sync is unavailable in developer attach mode. Launch the normal
  packaged Pitchblend-managed Geist runtime. — attach mode cannot mutate sync
  state in v1.0.
• Memory sync is available only in a packaged Pitchblend client in this
  release. — source builds are intentionally read-only for sync.
• This Geist database schema is not supported. Update Pitchblend before
  syncing. — install a compatible Pitchblend/Geist version; do not modify the
  database schema manually.
• This Geist memory embedding format is not supported. Update Pitchblend
  before syncing. — update Pitchblend before retrying.
• Secure credential storage is unavailable, so sync cannot protect this
  device's keys. — enable a protected operating-system credential backend.
  Sync must remain off until one is available.

Pairing or approval does not finish

• Create a fresh pairing code if the old one expired.
• Enter the code on the new device; do not reuse it on multiple devices.
• Compare the complete safety code on both devices.
• On the existing device, select Codes match, then Approve.
• Select Reject if the device label or code is unexpected.
• Keep both operating-system clocks accurate.

If two already enrolled devices are on the same LAN but cannot discover each
other, synchronize both clocks. Signed LAN announcements are accepted for only
60 seconds and tolerate at most 30 seconds of future skew.

Sync paused after a local database problem

Pitchblend can pause rather than risk losing data. Follow the message:

• Pitchblend paused memory sync after three failed attempts to recover a
  pending Geist update. No memory data was discarded. Restart Pitchblend after
  resolving local database access; if the problem persists, contact Pitchblend
  support.
• Pitchblend paused memory sync because a local runtime operation did not
  finish. Restart Pitchblend to resume memory sync.

Close other tools that may have the Geist database open, then restart
Pitchblend. Do not delete the encrypted journal; it may contain acknowledged or
pending change state needed for safe recovery.

Conflicts are reported

This is not data loss. Pitchblend keeps concurrent edits as separate memories
and reports No content was discarded. Open Geist, compare the copies, and
keep the version you want.

For normal setup, see
Account and Licenses and
Memory Sync. Developers can find
the opt-in diagnostics in
Developer Mode.