keybase / keybase/client

keybase cli remains running even after being disabled

Open
#2,845 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

Version: client 1.0.15

Steps to Reproduce

  • launchctl unload Library/LaunchAgents/homebrew.mxcl.keybase.plist
  • rm Library/LaunchAgents/homebrew.mxcl.keybase.plist
  • keybase id sneak

Expected Behavior

  • No keybase background process running after command exits

Actual Behavior

  • LaunchAgent plist file is re-created and re-loaded, leaving daemon running and respawning if killed

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the sequence with launchctl, the removed homebrew.mxcl.keybase.plist, and keybase id sneak. Trace the CLI and macOS LaunchAgent handling involved in recreating and loading the plist. Done means disabling and removing the LaunchAgent prevents a background process from starting or respawning.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, macos
Domain
cli, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.