Skip to content
arafat@ops:~/dashboard
Back to project archive[ MY BUILD / TermStream ]

$ cat ~/work/termstream/README

I keep the work running.

I built TermStream so a disconnect doesn't get the last word. My server, my workspace, my sessions, back in reach from a browser or phone.
ts.arafatops.com
Signal chain / TermStream walkthrough
  1. My dashboard. My call.
  2. I check the server first.
  3. I pick the exact workspace.
  4. I choose what runs.
  5. I pick up where I left off.

$ ls ~/work/termstream/brief

my design decisions / on display

I had a problem. I built the fix.

I wanted this.

Keep long-running engineering work available across devices without losing control of the server, repository, branch, or active session.

I built this.

  1. Choose and manage owner-scoped SSH servers.
  2. Attach repositories and select isolated branch workspaces.
  3. Launch Shell, Claude, Antigravity, Codex, or Python sessions.
  4. Return to persistent work and use remote session controls.

$ ls ~/work/termstream/screens

my product / use arrows or swipe

I kept the receipts.

My build / TermStream

My dashboard. My call.

01 / 05

TermStream dashboard showing server selection, workspace controls, and agent launchers
See the active server, choose a workspace, launch the right tool, and return to running work from one dashboard.
[ I've shipped 40+ projects. ]

Bring me a better problem.

I've built persistent terminals and connected knowledge systems. Bring me the workflow, the constraints, and the parts everyone keeps working around.

Schedule Engineering Review$ ./connect.sh --secure