isehgal
Joined 3 years ago
Karma
6
Submissions
22
Member since
Apr 13
Recent submissions
Comment · 10 days ago
appreciate it!
Comment · 11 days ago
nice, this is close to something we run ourselves. we put up examples of sm agents that scan socials daily for keywords and DMs us (docs here https://docs.omnara.com/examples/x-signal-agent). probably the fastest starting point is to point your agent to it and ask it to swap in your keywords
Comment · 11 days ago
thanks swyx! the log is the agent is a core insight behind this
Comment · 2 months ago
have you found different providers excel in different things?
Comment · 7 months 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
Comment · 8 months 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 it comes to long running tasks and the edge cases that show up in real use.
Comment · 8 months ago
Really appreciate that means a lot. Excited for what’s ahead
Comment · 8 months 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 because we need access to sync across devices, send notifications, and resume agents. Cloud sandboxing is opt-in and would require syncing codebase state.
Comment · 8 months 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
Comment · 8 months 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, worktrees, sandboxing, richer git management (diffs, checkpoints), and preview URLs. Would love to hear what you think if you give it a spin :)
Comment · 8 months 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 locally on your machine.
We've heard this from other users and it's on our roadmap. The challenge is we're building features like voice coding agents and hosted sandboxes that require plaintext inputs, so we'd need two execution models. Doable, but adds complexity for our team size.
That said, it's something we're prioritizing as we grow. No promises on timing, but it's coming.
If you want to discuss specific requirements or a local-only mode, happy to chat: https://discord.gg/Dc46sYk6e3
Comment · 8 months ago
yes you got the point here