docs

Other commands

div projects

List the projects you've published to div.so.

div projects

A quick inventory — the projects you've deployed from this account, with their public URLs.

#Synopsis

div projects

No flags. No prompts. Just the list.

#What it does

div projects calls the Div API with the personal access token saved on this machine and returns the projects owned by your account, most-recently-updated first. Each row prints the project's name and its {slug}.div.so URL.

my-portfolio       —  https://my-portfolio-a4f9d2.div.so
weekend-prototype  —  https://weekend-prototype-b3c5e1.div.so
launch-page        —  https://launch-page-9zk2d7.div.so

If you've signed in but haven't published anything yet, you'll see an empty-state message instead:

No projects yet. Run div deploy to publish your first one.

#When it's useful

  • You forgot what slug a project landed on.
  • You want a quick mental inventory before deciding what to update next.
  • You're on a fresh install and want to confirm the CLI knows who you are.

#Requirements

You need to have completed at least one div deploy from this machine and clicked the verification link in your inbox. That handshake is what saves a personal access token locally — without it, the command can't authenticate.

If the CLI has no saved session, you'll see:

Not logged in. Run div deploy to get started.

If the CLI does have a session but the server doesn't recognize the token any more (rare in production; common in local dev after a database reset), you'll see:

Your session has expired. Re-run div deploy to sign in again.

The stale token gets cleared automatically after that first 401 — your next div whoami will correctly say "Not logged in" until you re-verify through a new deploy. See Troubleshooting for the full recovery path.

#See also