GH-CODESPACE-LIST(1)

💅 gh-codespace-list — the manual page, but make it make sense

okay so real quick — this is the gh-codespace-list page straight out of the GitHub CLI manual (we're on v2.102.0, don't @ me). Let's get into it bestie ✨

---

✨ NAME ✨

gh-codespace-list — literally just, like, list your codespaces 🎀

---

🦋 SYNOPSIS 🦋

gh codespace list [flags]

that's it. that's the whole vibe. flags are optional, the codespaces are not 💀

---

🌸 DESCRIPTION 🌸

It lists the codespaces that belong to the authenticated user — aka you, the main character 👑.

Alternatively, if you're an organization administrator, you can list all the codespaces that are billed to the organization. like, all of them. the whole collection. slay for the admins fr fr 💖

just clocking that "organization administrators may" — that's an admin-only situation, not a you-situation unless you're actually an admin.

---

🎀 OPTIONS 🎀

• -q, --jq <expression> — filter the JSON output using a jq expression. yes you can pipe-and-jq it, icon behavior honestly 🔥
• --json <fields> — output JSON with the fields you specify. you pick 'em, it prints 'em ✨
• -L, --limit <int> — max number of codespaces to list. default is 30 — so yes, there's a cap by default, that's not a bug 🫶
• -o, --org <login> — the login handle of the organization you want to list codespaces for. heads up: this one's admin-only 👑
• -R, --repo <string> — repository name with owner, formatted like user/repo. keep the slash, bestie 💅
• -t, --template <string> — format the JSON output using a Go template. for the details, see gh help formatting 🦋
• -u, --user <username> — the username to list codespaces for. this is used with --org, so they're a duo, not a solo act 🫶
• -w, --web — list codespaces in the web browser instead. cannot be used with --user or --org — pick a lane ngl 🚫

---

🌈 ALIASES 🌈

because typing the whole thing is so much effort:

• gh codespace ls
• gh cs ls

short, sweet, iconic ⭐

---

💜 JSON FIELDS 💜

these are the fields you can get out of --json, in the exact order the page gives 'em:

• createdAt
• displayName
• gitStatus
• lastUsedAt
• machineName
• name
• owner
• repository
• state
• vscsTarget

no cap, that's the whole list 🍓

---

🧚 EXIT CODES 🧚

so you know what happened when it's done:

• 0 — Successful execution 🎉
• 1 — Error 😭
• 2 — Command canceled 🙈
• 4 — Authentication required (go log in bestie) 🔑

NOTE: Specific commands may have additional exit codes. Refer to the command's help for more information. so like, don't come for me if there's a fifth one — check gh help 💀

---

🔥 SEE ALSO 🔥

• gh-codespace(1) — the big sibling page, go read it 🫶

---

okay that's the whole thing! sourced from the GitHub CLI manual, v2.102.0, dated Oct 2026 — and yep, that's genuinely what GH-CODESPACE-LIST(1) says at the bottom. mwah 💋✨