[BUG] Authentication is not working

[modelnova-ai]

Describe the Bug

Authentication is not working on the web login page. I am unable to log in using custom credentials or random username and password combinations. The page always shows "Authentication failed".

---

To Reproduce

1. Run the server using
   occ start

2. Open the web UI at
   http://127.0.0.1:3000/auth/login

3. Enter any username and password

4. Click Sign In

5. Observe the error message

---

Expected Behavior

I expected to be able to log in using valid credentials

Actual Behavior

The login page always returns "Authentication failed" regardless of the credentials entered.

Container logs show authentication attempts but no successful login:

Environment

OS: macOS
Installation method: npm global install
Node version: v22.15.0
Browser: Chrome

[pRizz]

When running this from the opencode-cloud cli, you must configure users that will be available in your container with the "user add" subcommand:

opencode-cloud user add myuser

I will make this more clear in the docs and the web ui. Thank you for pointing this out.

[modelnova-ai]

@pRizz thanks, after adding the user configuration it is working now. Thanks for that.

I am having trouble mounting my local project folder. I ran this command to add the mount:

occ mount add /Users/Desktop/opencode:/home/opencode/workspace

Added mount: /Users/Desktop/opencode -> /home/opencode/workspace (rw)

The mount shows as added, and I restarted the container, but inside the container the /home/opencode/workspace directory is still empty. I do not see my project files there.

Am I missing a step to make the local folder contents appear inside the container?

[pRizz]

Thanks for reporting this. You weren’t doing anything wrong — this exposed a real CLI behavior gap.

Root cause:

1. occ mount add told users to “restart”, but occ restart previously preserved existing container mounts and did not apply new mount config.
2. It was also possible to accumulate multiple mounts targeting /home/opencode/workspace, which can cause mount-application problems on recreate.

Please upgrade your opencode-cloud installation with npm i -g opencode-cloud@latest. What we changed:

• occ mount add now treats container target conflicts as replacement (upsert) and explains what was replaced.
• occ restart now detects mount config drift and prompts to recreate the container so mount changes are actually applied.
• In --quiet, restart now fails with actionable instructions instead of silently keeping old mounts.
• Docs now include a dedicated workspace-mount section with apply/verify steps.

Workaround (also now the recommended flow):

occ mount add /Users/<username>/Desktop/opencode:/home/opencode/workspace
occ restart
# if prompted, confirm recreate
occ status

[modelnova-ai]

Nice work on the fix. I updated and mounts are working properly now. Thanks for jumping on it fast.

I have a few simple UX suggestions after using it along with the current README flow.

Authentication flow

• Setup mentions IOTP, passkeys, PAM, and CLI users, but it feels split between browser steps and terminal user commands
• After initial setup, the web app should always show a login screen and never open directly without auth
• Credentials created during first time setup should clearly be the main way users log in later, without confusion about needing extra occ user steps

Simpler first run experience

• First time occ start could guide everything in one flow
• Pull image, start container, guide user through IOTP and passkey or password setup, then confirm system is ready
• After that, users should not need to think about container setup or user management for normal usage

Auto mount current folder

• Right now mounting requires occ mount add plus occ restart, which feels heavy for a common action
• After setup, when a user runs occ inside any project folder, the CLI could automatically mount the current directory into
  /home/opencoder/workspace/
• If needed, occ could auto recreate or restart the container to apply the mount

Smoother daily workflow

• First time

  • Run occ start
  • Finish login setup in browser

• After that

  • Go to any project folder
  • Run occ
  • Folder auto mounts and container starts if needed
  • Opening the URL always asks for login

This would reduce a lot of manual steps while keeping advanced commands for power users. Does this direction make sense for the future UX?