UPTERM(1)
π 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 forinfo. 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=falseshows 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-emptyDEBUGturns 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 β
upterm-session(1)β go read the family page, bestie π¦
π 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
- arch rolling: upterm 0.41.0-1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms