26

Every time I launch the native Figma app on macOS (macOS 13 Ventura) I get this notification:

Login Item Added: "FigmaAgent.app" will open automatically when you log in. You can manage this in Login Items Settings.

Notification on macOS

And following the instructions on the notification I can remove the Login Item as expected, but I will get the notification again next time I launch the app, and the Login Item will be added once more.

Login Item Settings with FigmaAgent.app on the list

I want to remove it and never to be added again. How can I do that?

Pd: I reached out to Figma support a few times, and they mostly ignored my messages, and when I asked why was I being ignored they gave me a rather unhelpful answer:

Hey there, sorry for the delay & confusion. We didn't reply, because the answer was in your original tweet. Sorry if it wasn't obvious, but in the screenshot, you manage it from Login Items Settings: Apple menu > System Settings, click General in the sidebar, then Login Items.

To be very clear, I don't want to know how to remove FigmaAgent from Login Items, I want to know how to prevent it for being added again.

vicegax
  • 4,709
  • 28
  • 37

2 Answers2

18

From https://twitter.com/qdoug/status/1374785043504185351:

This seems to work for removing FigmaAgent:

  • Force Quit it in Activity Monitor

  • Remove it in System Preferences -> Users & Groups -> Login Items

  • Delete ~/Library/Application Support/Figma/FigmaAgent.app

  • Delete /Applications/Figma.app/Contents/Library/FigmaAgent.app

  • touch "~/Library/Application Support/Figma/FigmaAgent.app" to stop it being re-enabled by updates

zjames
  • 729
  • 11
  • 14
  • any idea how they are programmatically adding it in Login Items? – Er. Khatri Jan 30 '23 at 08:20
  • @Er.Khatri I'm aware of two ways to do this. One is through the deprecated `LSShareFileListInsertItemURL` api that can be set up in the app delegate during launch. The new way available as of Ventura (I think) is a framework called [SMAppService](https://developer.apple.com/documentation/servicemanagement/smappservice). I'm not sure which approach Figma uses. – zjames Feb 06 '23 at 01:05
  • Nice! Hopefully this doesn't need to be done again after an update? – derpedy-doo Feb 07 '23 at 01:59
  • 1
    @derpedy-doo Deopending on how they deploy updates, I'm afraid it may return. Hopefully they will address the lack of an option to disable it. If they don't one solution would be to create a plain file with the same name where the application wants to create the app bundle (after deleting it): `touch "~/Library/Application Support/Figma/FigmaAgent.app"`. Not tested! – zjames Feb 08 '23 at 18:57
  • 1
    Looks like this must be done after every update. – derpedy-doo Mar 03 '23 at 01:47
  • 1
    The solution below this one works through updates, unlike this accepted answer. – Katerberg Jul 24 '23 at 17:30
  • @Katerberg that is true, but see my comment in reply to derpedy-doo above which also solves the update problem. – zjames Jul 25 '23 at 16:12
  • @zjames not quite. if you just create the dummy file Figma will override it later. It is also not a good idea to delete the file inside the Figma.app itself as that also gets replaced with updates. – marcaux Aug 03 '23 at 14:10
  • @marcaux You can't overwrite a plain file with a directory so it persists, takes one less step and doesn't require you to be an admin user. – zjames Aug 03 '23 at 18:42
  • @zjames are you sure? in my tests when the file is not marked as undeletable it will get deleted and replaced by figma. – marcaux Aug 13 '23 at 14:28
18
removing FigmaAgent.app
  • rm -fr ~/Library/Application\ Support/Figma/FigmaAgent.app
creating a dummy file
  • touch ~/Library/Application\ Support/Figma/FigmaAgent.app
make the file undeletable
  • sudo chflags -R schg ~/Library/Application\ Support/Figma/FigmaAgent.app

Now Figma will not be able to override that file when it wants to update it and you don't have to fiddle with the .app everytime Figma updates itself.

Also the login item does not get created for me again after removal at this point.

marcaux
  • 181
  • 1
  • 3
  • 2
    In addition to the accepted answer, this indeed prevented FigmaAgent to appear after every update. And updates seem to work fine for me. – vicegax Apr 22 '23 at 09:11