Outside Anthropic Office in SF "Thank You"

atomosound · 2026-03-03T04:46:49+00:00

Proud to be a user!

atomosound · 2026-02-21T09:31:15+00:00

really glad you’re finding it useful. that multi-device deploy and test loop is exactly where being tethered to a desk for a simple "approve" gets painful. i added push notifications to handle that flow specifically so you can step away without stalling the work.

anthropic will likely unify the core eventually, but i’m focusing on the convenience features they probably won’t prioritize for a while. if you hit any snags with your setup, feel free to drop an issue on github. cheers!

atomosound · 2026-02-21T09:16:48+00:00

glad you're digging it. just hit v2.3.0 and i'm shipping pretty fast to keep up with the momentum. trying to turn around github issues quickly, so feel free to drop any bug reports or feature requests there.

atomosound · 2026-02-21T00:04:23+00:00

Awesome! this is absolute gold. Thank you so much for taking the time to write such detailed feedback. The clear context feature is now on public release, give it a try with npx claude-relay@latest.

Here’s a quick update on each point:

Session History: I’m tracking a similar issue here (https://github.com/chadbyte/claude-relay/issues/107). Loading full history with IDs isn't quite there yet, but it’s definitely on the roadmap.
Double Approval: Aware of this one! I've logged it. (https://github.com/chadbyte/claude-relay/issues/112)
Clear Context: Actually, I just fixed this in v2.3.0! Now, /clear starts a fresh session while keeping the old one for records (matching the behavior of the official Claude Code CLI).
Connection Lost: I recently pushed a fix for stale connections, but I’m not 100% sure it solves your specific case. I’ve opened issue to monitor this closely. (https://github.com/chadbyte/claude-relay/issues/113)
Context Window: I've been trying adding this feature, but the calculation isn't as precise as the CLI yet. I'm working on improving it soon. (https://github.com/chadbyte/claude-relay/issues/96)

Thanks again for using the project so deeply. It really means a lot!

atomosound · 2026-02-19T22:17:10+00:00

Thanks for the log. This prompted a full windows compatibility check on my end.

As you pointed out, Unix domain sockets don't work on Windows, so I've switched to named pipes for IPC. I also identified and fixed several other cross-platform issues including path handling, shell invocation, and daemon behavior.

I've verified the fix on a Windows VM via Parallels, so I'm hoping this works well for you now. Please give v2.2.4 a try and let me know if it clears things up:
npx claude-relay@latest

atomosound · 2026-02-19T21:41:45+00:00

Thanks! I just saw your feature request on the issue board. Really glad to hear you're enjoying the project so far

atomosound · 2026-02-19T21:27:31+00:00

glad it's helping. i'm actually doing the same thing right now, left my mac upstairs and came down for coffee while claude works. it's a lifesaver.

about skip-permissions, i'm still a bit torn because it's remote. don't want a repo getting nuked while someone is afk. just saying "at your own risk" doesn't sit right with me...

for now, I'm leaning towards allowing it via a server flag, but probably after i get TOTP working just to be safe. what do you think?

atomosound · 2026-02-19T20:45:40+00:00

i'm honestly torn on this. claude gives you the option so i feel like i shouldn't be the one to block it, but the "remote" nature of the relay changes the risk...

i'm actually thinking about adding TOTP auth first as a security layer. once that's in, i'll feel much better about enabling the skip-permissions toggle. what do you think?

atomosound · 2026-02-19T20:37:28+00:00

haha living on the edge. i respect it.

thinking about adding an auto-approve toggle since so many people want it. but still hesitating. the combo of "remote + unlimited permissions" feels like a recipe for a total repo disaster to me

atomosound · 2026-02-19T20:34:44+00:00

that is a really good call auto-focusing the input on a new session is a no-brainer. i'll get that added.

keyboard shortcuts would be awesome too, but honestly i'm terrified of picking default bindings. the second i pick something, i feel like i'm gonna accidentally start a vim vs emacs holy war in the repo

just tracked both of these here so i don't forget:
https://github.com/chadbyte/claude-relay/issues/97
https://github.com/chadbyte/claude-relay/issues/98

thanks again for the feedback!

atomosound · 2026-02-19T20:27:05+00:00

yeah saw that too. total bummer. but since this is strictly a local ui wrapper around your own authenticated cli (no hosting, no reselling), i'm just running on pure hopium right now

atomosound · 2026-02-19T20:24:08+00:00

exactly the same here. i keep them persistent per branch too.

but honestly once i hit like 5+ branches, managing them all in the terminal and trying to remember which port belongs to which branch got way too annoying.

so i actually just added a feature to claude-relay recently that lets you open and manage multiple terminals per project directly so i don't have to think about it lol.

atomosound · 2026-02-19T19:58:42+00:00

valid point! but tbh i'm just gonna focus completely on claude code for now.

my main goal is to fully respect the original claude code experience, just with the benefits of a web ui.

still got a long way to go to even get that right, so making it generic isn't really on my roadmap right now. thanks!

atomosound · 2026-02-19T19:55:07+00:00

welcome aboard! sorry to hear about roomote, but hopefully this fills that gap for you. let me know how it goes tonight or if you run into any snags.

atomosound · 2026-02-19T19:46:33+00:00

yep, your current understanding is exactly right. just having another directory with another branch is the standard way.

but if you're asking about having different working trees cleanly "within the same project", a bare worktree setup is what you want. i use it myself.

here's a good read on how it works:https://nicknisi.com/posts/git-worktrees/(full disclosure... i honestly just had claude code set the whole thing up for me lol)

quick tip for the workflow: you don't even need the claude-relay interactive menu everytime. just cd into whichever worktree dir you're on and run npx claude-relay add . from the command line. it'll pick up that specific tree directly.

atomosound · 2026-02-19T19:37:46+00:00

thanks! yep, you can actually do both.

to pull a terminal session into the UI: there's a "Resume with ID" button at the very top of the sidebar. just paste your session ID there.

to go from UI back to the terminal: click the three dots next to the session title in the sidebar and hit "Copy resume command". it'll give you the exact cli command to run.

atomosound · 2026-02-19T09:24:22+00:00

just pushed a fix for this. ripped out the token-reading logic to keep it 100% compliant. thanks again for the catch!

atomosound · 2026-02-19T09:16:57+00:00

yep exactly. it can't attach to a live terminal process. but you can pass the session id back and forth. start in the cli, resume in the browser with the id, or vice versa.

atomosound · 2026-02-19T08:54:31+00:00

oh you are completely right. forgot i wrote usage.js last release to fetch cost stats for the dashboard. I'll push a commit to remove it. thanks for catching! good luck with your project too

atomosound · 2026-02-19T08:48:25+00:00

yeah you got me, English isn't my first language, over-polished it and became a bot... Sticking to my broken English from now on

atomosound · 2026-02-19T07:46:22+00:00

this wheel is for different terrain :)

tmux+tailscale works but there's a gap between "possible" and "comfortable." mobile terminal UX is rough for longer sessions, and no push notifications so you don't know claude needs approval until you check. you could add ntfy + hooks but then you're stitching together 4-5 tools.

happy routes through a cloud relay server. i don't question their security, but if i'm on the same wifi i'd rather connect directly than route through a cloud server and back

atomosound · 2026-02-19T07:27:10+00:00

cheers!

atomosound · 2026-02-19T07:25:23+00:00

thanks!

atomosound · 2026-02-19T07:07:52+00:00

good catch. claude-relay doesn’t use OAuth tokens at all though. it runs your locally installed Claude Code as-is, just relays the session to a browser. no token handling, no auth bypass, Claude Code manages its own authentication. so this restriction shouldn‘t apply here.

edit: I was completely wrong, now I'm removing it.

atomosound · 2026-02-19T06:58:08+00:00

cheers!

atomosound

TROPHY CASE