[BUG] claude remote-control fails with "Workspace not trusted" even after accepting trust dialog in interactive session

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Environment:

Claude Code version: v2.1.81
OS: macOS
Plan: Claude Max

What happened:
Running claude remote-control from a directory that is already trusted fails with:
Error: Workspace not trusted. Please run claude in /Users/myusername first to review and accept the workspace trust dialog.
Steps to reproduce:

Run claude in /Users/myusername — the trust dialog never appears, session starts normally
Exit with /exit
Run claude remote-control from the same directory
Error appears despite the directory being trusted

Why this is a bug:
The directory /Users/myusername is already present in ~/.claude.json under projects:
json"projects": {
"/Users/javierdiaz": {
"allowedTools": [],
"mcpContextUris": [],
"mcpServers": {},
"enabledMcpjsonServers": []
}
}
The claude remote-control subcommand appears to have a different trust resolution path than the interactive claude session — it does not correctly read existing trust from ~/.claude.json.

What Should Happen?

claude remote-control should read trust from ~/.claude.json the same way the interactive session does.

Error Messages/Logs

Steps to Reproduce

Run claude in /Users/myusername — the trust dialog never appears, session starts normally
Exit with /exit
Run claude remote-control from the same directory
Error appears despite the directory being trusted

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

v2.1.81

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_