[Bug]: Built-in Git sync fails when using external SSH agent (e.g. Proton Pass)

[nexeck]

Preflight

• I searched existing issues and this isn't a duplicate
• I'm on the latest version (or I've noted my version below)

What happened?

Describe the bug

The built-in Git synchronization in OpenKnowledge fails

to push/pull/sync when SSH keys are managed and provided
by an external SSH agent (such as the Proton Pass SSH
agent or 1Password SSH agent).

It seems the built-in Git integration does not fully

respect or forward the SSH_AUTH_SOCK environment
variable to authenticate git actions, causing
connection/permission errors when interacting with remote
repositories.

### Expected behavior
OpenKnowledge should respect and forward the standard

SSH_AUTH_SOCK environment variable to its underlying
git runner so that authentication via active SSH agents
works out-of-the-box.

### Environment
- OS: macOS
- OpenKnowledge version: 0.32.0 (based on project

state)

Steps to reproduce

1. Configure an external SSH agent (e.g., Proton Pass)

and verify that CLI-based git commands (like git push)
work normally in the system terminal.
2. Open an OpenKnowledge workspace backed by a Git
repository with an SSH remote.
3. Attempt to trigger a sync, edit, or check history.
The operation fails or times out because it cannot access
the SSH keys via the agent.

Platform

macOS (Apple Silicon)

How did you install OpenKnowledge?

Desktop app (DMG)

Version

0.32.0

Logs, errors, or screenshots

[miles-kt-inkeep]

Thanks for the issue, we are taking a look at this.

[nexeck]

Not sure if related to this.

GitHub Account is connected, can't Openknowledge use the GH API/SDK for comitting/push?

When GitHub Account isn't connected, why is Git Autosync disabled? It could just use the existing git configuration, it it seems to use anyway.