Access NoteCove Remotely
notecove serve forwards your local NoteCove desktop app to a remote machine over SSH, so the CLI on the remote works as if the app were running there.
Prerequisites
- NoteCove desktop app running locally
notecoveCLI installed on the remote machine- SSH access to the remote (key-based auth recommended)
- OpenSSH 6.7+ (for Unix socket forwarding)
Start the tunnel
On your local machine:
notecove serve --ssh user@remotehostNoteCove connects, establishes the socket forward, and prints the init command for the remote.
Initialize access on the remote
In a separate terminal, SSH into the remote and run the printed init command:
notecove init --profile <id> --project MYPROJApprove the request in your local NoteCove desktop app.
Use the CLI on the remote
The CLI now works normally on the remote:
notecove task list
notecove note search "design decisions"
notecove task create "Fix the deploy script"All commands go through the forwarded socket to your local app.
Stop the tunnel
Press Ctrl+C in the terminal running notecove serve. The tunnel closes and the remote registry entry is cleaned up automatically.
Extra SSH options
# Custom key and port
notecove serve --ssh user@remotehost --ssh-opts "-i ~/.ssh/mykey -p 2222"
# Skip host key checking (ephemeral hosts like Docker containers)
notecove serve --ssh user@remotehost --ssh-opts "-o StrictHostKeyChecking=no"Forward into a local Docker container
You can use notecove serve to project the CLI into a Docker container running on your machine:
# Start the tunnel to the container (assumes sshd is running in the container)
notecove serve --ssh root@localhost --ssh-opts "-p 2222 -o StrictHostKeyChecking=no"Then inside the container, run the notecove init command printed by serve and approve the request in your desktop app. The CLI inside the container now works as if NoteCove were running there.
Print-only mode
Run notecove serve without --ssh to print the manual SSH commands instead of automating them — useful for non-standard tunnel setups.