UPTERM(1)

πŸ“¦
version 0.41.0 Β· 2 versions
, in arch rolling

πŸŽ€ UPTERM(1) β€” the upterm manual, bestie edition πŸŽ€

okay so you're looking at the Upterm Manual, specifically the page for upterm-session-info, and honestly? it's a good one. let's get into it πŸ’…

✨ NAME ✨

upterm-session-info β€” show a session, given its name or session ID. that's it. that's the whole gig 🫢

🌸 SYNOPSIS 🌸

upterm session info NAME|ID [flags]

πŸ¦‹ DESCRIPTION πŸ¦‹

So you wanna see a session? say less. this command shows you a session given its name or session ID β€” literally all the deets: its status, how guests join it, who is connected, and what guests may do. the full vibe check, no cap ✨

NAME|ID is either the session's name (the one upterm host printed, or the one --name gave it) or its session ID. and if you're like "bestie where do I even find those" β€” upterm session list shows both. iconic. πŸ‘‘

One thing to know: a name is looked up before an ID. so if you've got something that could be either, the name wins. iykyk.

And plot twist β€” a session that has ended still answers you, pulling from the record it left behind: how it ended. it's giving ghosting but make it helpful πŸ˜­πŸ’€

πŸ’– Output formats πŸ’–

  • -o json β€” JSON. that's the one. that's the list.

πŸ“ Exit status πŸ“

  • 4 β€” exits 4 when no session has that name πŸ™ˆ
  • 1 β€” exits 1 for any other failure πŸ’€

🌈 OPTIONS 🌈

  • -h, --help[=false] β€” help for info. your little emergency exit when you're lost 🧚
  • --hide-client-ip[=false] β€” hides guests' IP addresses from upterm's output. and here's the nuance, bestie: when it isn't set (whether by flag, environment, or config file), they're hidden in CI only. and if you're like "no actually show me" β€” --hide-client-ip=false shows them there too. so you do have the power 🫢
  • -o, --output="" β€” output format: json. default is empty (""), so set it if you want it. lowkey important ✨

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

  • --debug[=false] β€” enables debug logging. the log file lives at /build/.upterm/upterm.log. also, a non-empty DEBUG turns it on too β€” so the env var is doing the same job. two paths, same slay πŸ”₯

πŸ’œ EXAMPLE πŸ’œ

okay real talk, examples are the main character here:

# Show the session named build:
upterm session info build
# The same session, by its session ID:
upterm session info d3k5fia7m4us73ehblug
# As JSON:
upterm session info build -o json

look at that. same session, three ways, all valid. ate πŸ’…


⭐ SEE ALSO ⭐


πŸŽ€ HISTORY πŸŽ€

2-Nov-2026 β€” Auto generated by spf13/cobra. yeah, it was built by the robot, we're just vibing with it πŸ€–βœ¨


ngl the one thing to keep in your head: name gets looked up before ID, and a dead session still spills its ending. periodt πŸ’€πŸ’–

and that's the page!! Upterm 0.0.0+dev, Nov 2026 β€” mwah, go show some sessions who's boss 🫢🌸

πŸ“¦ where this page comes from