Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
isehgal
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
isehgal
21d ago
have you found different providers excel in different things?
2.
▲
The Log Is the Agent
(omnara.com)
6 points
by
isehgal
3mo ago
|
0 comments
3.
▲
by
isehgal
6mo ago
we've run into this problem. when you're running 4-5 Codex/Claude Code sessions in parallel across worktrees, the port collision sucks. have to check out
4.
▲
The Five Ways to Control a Coding Agent from Your Phone (and Where Each Breaks)
(omnara.com)
4 points
by
isehgal
7mo ago
|
0 comments
5.
▲
by
isehgal
7mo ago
Omnara founder here. We’ve been building in this space for a while, and the issues listed here are exactly the hard parts: session connectivity, reconnection logic, multi-session UX, and keeping state in-sync across devices. Especially when
6.
▲
Opencode Commit: "Anthropic legal requests"
(github.com)
3 points
by
isehgal
7mo ago
|
1 comments
7.
▲
by
isehgal
7mo ago
Really appreciate that means a lot. Excited for what’s ahead
8.
▲
by
isehgal
7mo ago
Good question. We don't have E2EE yet (it's on the roadmap), so some level of trust in Omnara is required today. All repo operations happen locally on your machine. For messages/chat history: we store those encrypted at rest
9.
▲
by
isehgal
7mo ago
Totally get it, we're trying to minimize subscriptions too. Free tier gives you 10 sessions/month with no length limits, so you can actually get a decent amount done before deciding if it's worth paying
10.
▲
by
isehgal
7mo ago
Thanks for the shout! Happy looks solid - always great to see more options here. Anecdotally from users who've tried both, we've heard Omnara has better reliability and latency. We also layer on some features like web support, wor
11.
▲
by
isehgal
7mo ago
Fair concern. We don't have true E2EE yet because our service needs access to message content for cross-device sync, notifications, and agent execution. Everything is encrypted in transit and at rest, and all repo operations happen loc
12.
▲
by
isehgal
7mo ago
yes you got the point here
13.
▲
by
isehgal
7mo ago
thats a great stab :) We dig into this in the post, but the key distinction we landed on is that the trigger can be asynchronous without the agent itself being async. A cron job, webhook, or autonomous trigger is really about scheduling, no
14.
▲
by
isehgal
7mo ago
hey, ishaan here (kartik's cofounder). this post came out of a lot of back-and-forth between us trying to pin down what people actually mean when they say "async agents." the analogy that clicked for me was a turn-based telep
15.
▲
by
isehgal
1y ago
Nice setup, clever way to keep it moving without much manual intervention. Curious, do you review the logs in between, or is it more of a yolo “continue” each time?
16.
▲
by
isehgal
1y ago
yeah especially as models get better