Does Zed provider still work? Must it run locally on macOS?

[visense]

Hi, I deployed Anti-API v2.9.0 via Docker on a Linux server (Synology DSM).

When I try to add a Zed account, I get:

Zed.app is not installed in /Applications.

After reading the source code (src/services/zed/oauth.ts), I understand the Zed import reads credentials from the macOS Keychain via the security CLI, which obviously won't work in a Docker/Linux environment.

I have two questions:

1. Is the Zed provider still working reliably? I've seen reports (and experienced with zed2api) that the Zed accessToken expires after a while. Since Anti-API doesn't have a refresh mechanism for the Zed login credential (only the LLM token auto-refreshes), how long does the accessToken typically last before it expires?

2. Is local macOS deployment the only way to use Zed? For users running Anti-API on a remote Linux server/Docker, is the recommended workflow:

   • Run Anti-API locally on Mac → import Zed account
   • Copy the auth JSON file from ~/.anti-api/auth/ to the server
   • When the token expires, repeat the process on Mac?

   Or is there a better approach I'm missing?

Thanks for the great project!

[daveCode-dot]

Good catch on the macOS-specific limitation. You've correctly identified the bottleneck — the Zed OAuth flow uses security CLI which only works on macOS.

On your two questions:

1. Zed accessToken lifetime: Zed tokens typically expire after 7–30 days depending on account settings. There's no built-in refresh mechanism in Anti-API currently, so you'll hit expiry eventually on long-running remote deployments.

2. Recommended workflow for Linux/Docker:

   • Your workaround is the current practical solution: run Anti-API locally on Mac once to authenticate, then copy the ~/.anti-api/auth/ file to the server.
   • For token refresh before expiry, you have two options:
     a) Periodically re-authenticate on Mac and copy the updated auth file back
     b) Patch Anti-API to support manual token paste (many similar tools have this — you paste the Zed token directly instead of going through OAuth)

Better approach: Consider opening a feature request to add a non-OAuth flow for Zed (manual token input). This would:

• Enable remote deployment without periodic local Mac reauthentication
• Separate credential transport from credential acquisition
• Allow users to rotate tokens in Zed web console and just update the config file

The Zed v2 API should support bearer token auth directly, so the infrastructure is there.