Packs: made by everyone.

Everything people make in Apex travels as a pack: one file that carries a companion, a skill, a routine, a theme or an app, so someone else can add it to their browser with one yes.

Browse shared packs on GitHub

A pack file with Mochi, Pip and Bolt on it

What a pack can hold

  • Skills

    Ways of doing a task that the companion reuses by name.

  • Routine templates

    Scheduled requests others can switch on.

  • Site tweaks

    Changes to how one site looks or behaves.

  • Themes

    Accent colours for the browser.

  • Companions

    A look and a personality, under the companion art licence.

  • Connectors

    A direct line to a tool you use.

  • Apps and panels

    Small tools in a tab, the sidebar or the new tab page.

  • Commands and tools

    New commands, page menu items and tools for the companion.

In the community index today

The index is young: these are the packs in it so far, each reviewed in the open before it was added. Apex shows it under Packs › Browse.

PackWhat it addsWhat it can do
Writing helpers/tighten, /meeting-notes and /weekly-review, and a Friday review routine.Adds skills and a routine template. Nothing else.
Nordic accentsFour accent colours: Fjord, Lingonberry, Moss and Aurora.Adds accents. Nothing else.
Calm WikipediaEasier reading on Wikipedia.Changes how Wikipedia looks (CSS only).
CountdownsA sidebar panel and a new tab card for the days that matter.Keeps its dates in its own storage. Reads no pages and sends nothing.

Installing is always your decision

  • You see everything first. Every install shows what the pack can do, in plain words, and all of its code, before anything is added.
  • Its code runs in a sandbox. A pack reaches nothing but what its manifest asks for: no network, device or file access unless it is listed and you agreed.
  • It is signed. A pack carries its author’s signature, and Apex refuses an update signed by anyone else.
  • Companions write, people install. A companion can build and propose a pack. Only you can install one or grant a permission.

Make and share your own

  1. In Apex, describe the pack on Packs › New pack and a companion builds it with you, or choose Share as pack on a skill, site tweak, app or companion you already have.
  2. Test it, then choose Export on its draft. Apex signs the file with your own author key.
  3. Send the file to someone, or open a pull request on the community index to list it for everyone. The repository explains the steps and what reviewers check.

Building an app, a game or a world by hand? The guides, working examples and packing tools are in apex-apps, and the kit is described in docs/apps.md. More ways to build on Apex are on the developers page.

Companions you make from Apex’s parts may be shared, and sold, in packs, apps and worlds for Apex, under the Apex Companion Art License. A character of your own may be your brand’s mascot inside Apex, never outside it.

Come make something.

Apex is free and open source, for Mac and Windows. Download it, pick a companion, and build the first thing you’ve been missing.

Download Apex Free and open source. Runs on Claude with your own Anthropic API key. How to get started