❌

Normal view

How to List All Packages Installed with Homebrew on Mac

4 September 2026 at 21:03

There are many situations where you may wish to get a list of all Homebrew packages installed on a Mac, specifically that were installed using Homebrew, and not anything else.   If you’re not familiar, Homebrew is a popular command line package manager for Mac, and many advanced Mac users use it to install additional ... Read More

The post How to List All Packages Installed with Homebrew on Mac appeared first on OS X Daily.

How to Show Hidden Files on Mac With or Without Terminal

7 August 2026 at 11:12

You can show hidden files on Mac with a simple keyboard shortcut. You do not need Terminal, an administrator password, or advanced technical knowledge for the most common method.

macOS hides some files because they contain settings, app information, or system resources that people do not normally need to open. These items remain on the Mac, but Finder does not display them during regular use.

You may need to see them when following troubleshooting instructions, opening the hidden Library folder, managing website files, checking app settings, or finding data left behind by an uninstalled application. Once the files are visible, you should avoid deleting anything unless you understand its purpose.

Show Hidden Files Without Terminal

Finder has a built-in shortcut that reveals hidden files and folders instantly. It is the fastest method when you only need temporary access.

To show hidden files in the current Finder folder:

Finder > Open Any Folder > Command + Shift + Period (.)

The period is the regular full-stop key on the keyboard. You must press Command, Shift, and Period at the same time.

The folder will update immediately. Hidden items normally appear lighter or more transparent than regular files. This visual difference helps you recognize files that macOS does not usually display.

The shortcut works in most Finder locations, including the user’s Home folder and some folders on external drives. It can also work inside the Open and Save windows presented by Mac applications.

If you do not see any changes, try the shortcut inside your Home folder. The available hidden items depend on the apps and services used on the Mac.

To open your Home folder:

Finder > Go > Home

After the Home folder opens, use the hidden-file shortcut again. You may see items with names that begin with a period, including configuration folders created by applications.

Files beginning with a period are commonly called dot files. macOS and Unix-based applications use them to store settings and other information without filling normal folders with technical data.

The Finder shortcut acts as a visibility switch. Using it a second time conceals the files again.

To hide the files after you finish:

Finder > Open Any Folder > Command + Shift + Period (.)

Hiding the files does not delete them. Finder simply returns to its normal view.

A dark-themed Mac Finder window displays files and folders in the 76BPPrimary directory, with a blue gradient background and an Apple logo in the bottom right corner. The view also hints at advanced customization options commonly accessed through Mac Terminal commands, such as the ability to show hidden files within the Finder.
Image Credit: AppleMagazine

Open the Hidden Library Folder

The user Library is one of the most frequently accessed hidden folders on a Mac. It stores app preferences, browser information, caches, containers, saved states, Mail resources, and other data connected to the signed-in account.

You can open the Library directly without making every hidden file visible.

To open your personal Library folder:

Finder > Go > Press and Hold Option > Library

The Library option appears in the Go menu while you hold the Option key. Select Library before releasing the key.

This method opens the Library belonging to the current user. Its path is ~/Library, where the tilde represents the user’s Home folder.

The user Library is different from the Library folder located at the top level of the startup disk. The top-level folder contains resources that can be shared by different accounts, while ~/Library primarily contains information for the current account.

Deleting content from the Library can reset an app or remove locally stored information. If troubleshooting instructions tell you to remove a file, confirm its name and location before making any changes.

Open a Specific Hidden Folder

Finder includes a Go to Folder feature for opening locations that are difficult to find manually. It is useful when you know the folder’s exact path and do not want to reveal every hidden item.

To open the Go to Folder field:

Finder > Go > Go to Folder

You can also reach the same field with a keyboard shortcut.

To open Go to Folder from the keyboard:

Finder > Shift + Command + G

A small field will appear. Type or paste the path of the location you want to open, then press Return.

To open your personal Library:

Go to Folder > Enter ~/Library > Press Return

To open the hidden SSH folder in your Home folder:

Go to Folder > Enter ~/.ssh > Press Return

The .ssh folder stores information used by Secure Shell tools. It may not exist if SSH software has never created it on the Mac. Finder displaying an error for this path does not necessarily indicate a problem.

To open the Library shared by all users:

Go to Folder > Enter /Library > Press Return

Pay attention to the beginning of each path. ~/Library opens the Library inside the current user’s Home folder. /Library opens the shared Library at the top level of the startup disk.

You can also paste a longer path supplied by an app developer or support technician. Check the spelling carefully because similarly named folders may contain completely different data.

A dark-themed Mac Finder window on a Mac shows files in a folder called “BGs,” displaying image filenames, their sizes, types, and modification dates, with an Apple logo watermark at the bottom right. If you want to see even more details or show hidden files in this view, you can easily use Mac Terminal commands for extra control.
Image Credit: AppleMagazine

Show Hidden Files With Terminal

Terminal can change Finder’s hidden-file preference so concealed items remain visible until you change the setting again. This option is helpful during longer troubleshooting or development sessions.

Terminal is included with macOS and can be opened from the Utilities folder.

To open Terminal:

Finder > Applications > Utilities > Terminal

A Terminal window will appear with a text prompt. Enter the command exactly as presented and press Return.

To keep hidden files visible in Finder:

defaults write com.apple.finder AppleShowAllFiles -bool true && killall Finder

Finder will close briefly and reopen. This restart allows the new visibility preference to take effect.

The command does not change the files themselves. It tells Finder to display items that macOS normally conceals.

You can reverse the change at any time.

To hide the files in Finder again:

defaults write com.apple.finder AppleShowAllFiles -bool false && killall Finder

Finder will restart once more and return to its regular view.

If Finder does not behave as expected after changing the preference, you can remove the custom value. macOS will then use its default behavior.

To remove the custom hidden-file preference:

defaults delete com.apple.finder AppleShowAllFiles && killall Finder

Terminal may say that the preference does not exist if no custom value is stored. That message simply means there is no setting to remove.

See Hidden Files Only in Terminal

Terminal can list hidden files without making them appear in Finder. This can be helpful when checking whether a file exists while leaving Finder unchanged.

The ls command displays the contents of a folder. Adding -a includes hidden items, while -l displays details such as permissions, ownership, file size, and modification date.

To list visible and hidden items in your Home folder:

ls -la ~

The results appear inside Terminal. Names beginning with a period are hidden during normal Finder use.

To list the contents of the folder currently open in Terminal:

ls -la

These commands only display information. They do not delete or modify the files shown in the results.

Work Safely With Hidden Mac Files

A hidden file is not automatically unnecessary, suspicious, or safe to delete. macOS and installed applications conceal many items to protect settings and reduce clutter.

The .DS_Store file, for example, can store Finder display information for a folder. External drives may include folders such as .Trashes and .Spotlight-V100, which macOS uses for Trash and Spotlight features.

Removing the wrong item can reset an application, delete local information, interrupt syncing, or cause macOS to rebuild a database. Copy an item to a safe location before changing it when troubleshooting instructions require manual file work.

Some system folders remain protected even when Finder displays them. Showing hidden files does not bypass administrator permissions or System Integrity Protection. There is no need to disable Mac security features simply to view a hidden folder.

Applications can also contain internal resources. These files are stored inside an app bundle and are different from standard hidden files.

To view the internal contents of an application:

Finder > Applications > Control-click the App > Show Package Contents

Changing files inside an app bundle can prevent the application from opening. If you need one of its resources, copy that file elsewhere instead of editing the original.

When you finish working, return Finder to its regular view to reduce the chance of accidentally moving or deleting a configuration file.

To hide all revealed files with the Finder shortcut:

Finder > Open Any Folder > Command + Shift + Period (.)

 

The post How to Show Hidden Files on Mac With or Without Terminal appeared first on AppleMagazine.

Pasting Quoted Paths and Escaped Terminal Text

3 August 2026 at 21:35

Anthony Reimer:

When you are shell scripting or working in Terminal, sometimes you want a quicker way to enter the path to a file or folder, particularly if you have already navigated to it in the Finder. One way that works in Terminal is to drag the file or folder from the Finder onto the Terminal window, which then types the path into the current command. However, another method was introduced in El Capitan (OS X 10.11) that allows you to copy the full path onto the clipboard.

In Finder, you can hold down Option and choose Edit ‣ Copy Pathname.

Starting in macOS Sequoia, copying the path to the clipboard using the method described generates a path that can be directly pasted into the Terminal or a script and be interpreted as that path without further manipulation.

It adds single quotes and or escapes characters, but only if necessary.

There are certainly some people who are unhappy with this change in behaviour but most Mac Admins will not be among them.

You can get the unescaped path via AppleScript.

Anthony Reimer (via Miles Wolbe):

Graham Pugh pointed out that if you have text on the clipboard, you have the option of pasting that text “escaped” in Terminal. Simply copy the text from whatever source you choose (e.g., the output of an AutoPkg run, where paths are not escaped), then in Terminal choose Edit > Pasted Escaped Text or use the shortcut Command-Control-V.

[…]

As a bonus, this concept can be applied to a tip I learned from Armin Briegel a few years ago, namely that if you select something in Terminal that you want to then paste into the current shell command, you can skip the copy-paste dance and instead just press Command-Shift-V to do it in one step (or if you prefer menus, Edit > Paste Selection). If you add the Control key to that sequence, the text pasted is escaped (Edit > Paste Escaped Selection or Command-Control-Shift-V).

Meta lança Muse Code, agente de programação alimentado pelo novo modelo Muse Spark 1.2

5 August 2026 at 22:16

A Meta lançou hoje o Muse Code, seu primeiro agente de programação — o qual rivalizará com soluções como o Claude Code (da Anthropic) e o Codex (da OpenAI).

A nova ferramenta, assim como os assistentes supracitados, facilita a criação de aplicativos em uma única interface, permitindo gerenciar conjuntos de agentes digitais impulsionados por IA que auxiliam no processo de desenvolvimento de software.

Releasing Muse Code in beta today. It's a terminal coding agent that takes on complete software engineering tasks across large repos: planning changes, writing code, validating the results. Powered by Muse Spark 1.2, a coding-focused model update. pic.twitter.com/xqavk41w6v

— Mark Zuckerberg (@finkd) August 5, 2026
Estamos lançando o Muse Code em versão beta hoje. Trata-se de um agente de programação via Terminal capaz de executar tarefas completas de engenharia de software em grandes repositórios: planejar alterações, escrever código e validar resultados. Ele conta com a tecnologia do Muse Spark 1.2, uma atualização de modelo focada em programação.

Ainda que disponível inicialmente em beta, o Muse Code pode ser usado para realizar uma ampla variedade de tarefas, planejando alterações, escrevendo código e validando os resultados. Desenvolvedores podem utilizá-lo por meio de uma modalidade de pagamento conforme o uso (pay-as-you-go).

Ao contrário do Codex e do Claude Code, atualmente não existe um aplicativo dedicado para o Muse Code. Desse modo, ele pode ser instalado no macOS e no Linux a partir de um comando de uma única linha:

curl -fsSL https://dev.meta.ai/install.sh | bash

Ele também opera em conjunto com o mais novo modelo de IA da empresa, o Muse Spark 1.2 — o qual foi desenvolvido e treinado juntamente com o novo agente de programação, o que melhora o desempenho geral.

O Muse Spark 1.2 é uma atualização do Muse Spark 1.1, lançado no mês passado, trazendo melhorias na geração de código, depuração de cenários complexos, compreensão da base de código e fluxos de trabalho de ponta a ponta para desenvolvedores. O novo modelo também amplia significativamente o poder computacional de treinamento para tarefas de programação.

Muse Spark 1.2 has improved coding capabilities compared to its predecessor. We significantly scaled up training compute on coding tasks while expanding training environment diversity, delivering improvements in code generation, complex debugging, and end-to-end developer… pic.twitter.com/0cTSBe4paj

— AI at Meta (@AIatMeta) August 5, 2026

O Muse Spark 1.2 apresenta recursos de programação aprimorados em comparação com sua versão anterior. Aumentamos significativamente a capacidade computacional de treinamento em tarefas de programação, ao mesmo tempo que expandimos a diversidade de ambientes de treinamento, proporcionando melhorias na geração de código, depuração complexa e fluxos de trabalho de desenvolvimento de ponta a ponta.

O modelo foi treinado com o Muse Code para otimizar o desempenho quando utilizados em conjunto, com foco em tarefas como geração de repositórios completos, projetos de grande porte e pesquisa automatizada.

O Muse Spark 1.2 já está disponível no Muse Code e na Meta Model API.

Nova interface contextual da Siri AI é descoberta no macOS 27; veja como ativá-la

20 July 2026 at 16:35

A Apple está testando uma nova interface na beta do macOS Golden Gate 27 que exibe uma série de atalhos da Siri AI sempre que o usuário seleciona texto em um app qualquer.

Descoberta pelo usuário identificado como “pdfu” em uma comunidade do Reddit, a novidade está claramente inacabada, o que explica o fato de ela vir desativada por padrão nas versões mais recentes do sistema operacional.

Como é possível notar abaixo, a interface assume a forma de um popover que aparece no canto superior esquerdo da seleção feita pelo usuário. Além disso, os atalhos são contextuais, o que significa que ações diferentes poderão ser sugeridas dependendo do conteúdo em destaque.

Caso o usuário esteja trabalhando em um texto, o recurso exibirá atalhos relacionados às Ferramentas de Escrita (Writing Tools), só para citar um exemplo. Ainda de acordo com as informações, o recurso também pode sugerir ações como enviar um email, adicionar um número aos contatos, exibir um endereço no app Mapas (Maps) ou rastrear um voo.

Para testar a novidade, é necessário estar rodando a terceira beta para desenvolvedores ou a primeira beta pública do macOS 27. Feito isso, basta abrir o Terminal, rodar o comando a seguir e reiniciar o Mac:

sudo mkdir -p /Library/Preferences/FeatureFlags/Domain && sudo defaults write /Library/Preferences/FeatureFlags/Domain/WritingTools LightweightUI_macOS -dict Enabled -bool true

Para desativar a novidade (o que talvez se prove necessário, já que, como dito, ela ainda está inacabada e apresenta inconsistências), basta abrir o Terminal novamente, rodar o comando a seguir e reiniciar o Mac:

sudo defaults write /Library/Preferences/FeatureFlags/Domain/WritingTools LightweightUI_macOS -dict Enabled -bool false

Como essa nova interface já está disponível (mesmo que escondida) nas betas do macOS 27, é bem possível que ela dê as caras em uma futura versão de teste do sistema — provavelmente em um estado bem mais polido.

via iThinkDifferent

Fix @unknown Terminal Prompt in MacOS

5 July 2026 at 17:02

Some Mac Terminal app users may find that their zsh prompt and Mac host name at the command line randomly sets itself to “@unknown”, or some variation of that. Opening the Terminal, you might find your prompt is something like “@unknown92844982″, @unknown184Afb84.home”, @UNKNOWN, or some variation of “@unknown” with a bunch of alphanumeric characters on ... Read More

The post Fix @unknown Terminal Prompt in MacOS appeared first on OS X Daily.

Novo malware usa CAPTCHA falso para roubar senhas no macOS

17 July 2026 at 20:21

Pesquisadores da Group-IB apontaram a existência de um novo malware para macOS chamado ClickLock Stealer, que usa uma falsa verificação da Cloudflare para enganar os usuários, roubando dados sensíveis.

Mirando usuários na Itália, nos Estados Unidos, na Jordânia e no Reino Unido, os criminosos iniciam o ataque simulando uma verificação de CAPTCHA da Cloudflare e, na sequência, convencem a vítima a copiar e colar um comando no Terminal do Mac.

Após a execução, o malware é instalado enquanto exibe uma falsa tela de progresso. Se o usuário optar por tentar interromper a instalação ou não seguir de alguma forma com o processo, ele fecha todos os aplicativos visíveis, deixando apenas uma janela para inserir a senha do macOS. O ciclo de insistência do software pode passar dos 3 dias (algo em torno de 83 horas, segundo o estudo).

Depois de instalado, o malware começa a coletar senhas de navegadores, extensões de carteiras de criptomoedas, arquivos de carteiras digitais, dados de gerenciadores de senhas e outras informações comprometedoras.

Segundo os especialistas, o ClickLock Stealer começou a ser distribuído em maio passado, passando despercebido por todos os mecanismos de pesquisa até recentemente. Ele foi identificado em 33 países, em sua maioria europeus, sem veiculação a algum grupo de crime cibernético, distribuído muito possivelmente por uma campanha de engenharia social do tipo ClickFix.

O estudo recomenda aos usuários que nunca colem comandos de websites no Terminal, independentemente de como a página se parece ou do que ela alega fazer, e a nunca entregar a sua senha a espaços extraoficiais (como comandos) — caso você perceba que a execução de outros aplicativos está sendo encerrada. Se você desconfiar que a sua máquina foi infectada com o malware, revogue as sessões dos seus navegadores e altere todas as credenciais potencialmente comprometidas.

via Macworld

Ars Asks: Share your shell and show us your tricked-out terminals!

I spend more time today than ever before interacting with terminal windows, which is something I don't think Past Me would have believed in the early '90s. Back then, poor MS-DOS was the staid whipping boy of the industry, and at least on the consumer side, graphical environments like Windows (and maybe even odder creatures like AmigaOS) seemed poised to stamp the command line into oblivion, leaving text interfaces behind as we all blasted into the ooey-GUI future.

As it turns out, though, the command line is still the best tool for some jobs—many jobs, in fact. I read a wise post some years ago (probably on Slashdot) arguing that a mouse-driven point-and-click interface essentially reduces the user to pointing at something on the screen and grunting, "DO! DO THAT!" at the computer. (The rise of right-click context menus adds the ability for the user to also grunt "MORE THINGS!" but doesn't otherwise add vocabulary.)

The command line, by contrast, gives the user the opportunity to precisely tell the computer what they want done, using words instead of one or two gestalts that the computer must interpret based on context.

Read full article

Comments

© Aurich Lawson | Getty Images

❌