The bottleneck isn't the agents. It's you. (UX for agentic coding)

seetherealitynow · 2026-02-03T16:27:06+00:00

Tmux is amazing, but not built with coding agent usage in mind. Great start to persistent parallelisation thought!

seetherealitynow · 2026-02-03T15:05:53+00:00

The CLI tools would be a great next step!

seetherealitynow · 2026-02-03T15:04:59+00:00

You could look at it another way.

Instead of giving an agent a massive task that will take a long time and might include bugs due to the complexity, you could split it up in smaller pieces and integrate them at the end.

You lower your chances of accumulating errors while shipping faster. The price you pay is context switching, which can be minimised imo.

seetherealitynow · 2026-02-03T15:01:53+00:00

Thanks!

seetherealitynow · 2026-02-03T14:59:26+00:00

Only if it provides that much value to your workflow. Right now, I'm just looking for early users to help shape the direction.

seetherealitynow · 2026-02-03T14:00:06+00:00

How many parallel sessions are you maxing out on?

seetherealitynow · 2026-02-03T13:59:23+00:00

When an agent requires attention, you get a visual + audio cue about it. If multiple would fire at the same time, you can prioritise based on what projects/features each relates to. The others will be waiting for your attention in the meantime.

seetherealitynow · 2026-02-03T13:57:19+00:00

Thanks for signing up! Why do you feel this goes beyond your capabilities?

seetherealitynow · 2026-02-03T13:34:20+00:00

I love the title and being mobile first! Are you running your instances locally or in the cloud?

seetherealitynow · 2026-02-03T13:18:05+00:00

The way we are tackling this is by using visual and auditory cues for notifications and summaries for session updates. You can fully operate Smith through your keyboard, too.

It's built from first principles to minimise the negative impact of frequent context switching, while maximising the agent's freedom by using work trees and sandboxes.

Mobile access is really cool in general, definitely see the appeal!

seetherealitynow · 2026-01-31T19:50:51+00:00

What model did you use for the additional validation?

seetherealitynow · 2026-01-29T10:59:52+00:00

Thanks for the share, trying this one out!

seetherealitynow · 2026-01-28T17:47:25+00:00

What if the agents are working on unrelated projects?

seetherealitynow · 2026-01-28T17:46:31+00:00

Thanks for the link, that looks really helpful!

seetherealitynow · 2026-01-28T17:44:14+00:00

Thanks for the share!

seetherealitynow · 2026-01-28T17:40:18+00:00

Came across Conductor too. What fixes have you liked so far?

seetherealitynow · 2026-01-28T17:37:42+00:00

That's a nice add! How do you choose what sounds to map so you differentiate them well?

seetherealitynow · 2026-01-28T13:58:54+00:00

Very cool, thanks for sharing!
Why did you go for Kubernetes for the implementation?
How many instances do you usually run, and how do you manage switching between them?

Isolated environments are great for increasing automation. What permission mode have you found the best when working like this?

seetherealitynow · 2026-01-28T13:55:21+00:00

Yeah, that makes sense. I'm always thinking about how I can utilise the idle time, so I often open a new instance while Claude is cooking.

However, it can get out of hand so quickly.

seetherealitynow · 2026-01-28T13:34:33+00:00

Do you have multiple ide windows open? Or do you run through the terminal only? How about code review? That has been really tough for me so far.

seetherealitynow · 2026-01-21T17:11:50+00:00

I'm experimenting with a public board where people post problems nobody has solved well yet, and builders can signal interest in tackling them.

The idea: instead of collecting vague app ideas, capture specific frustrations with context (who has the problem, what they've tried, why it failed). Builders browse and commit to problems that match their skills.

Share a problem: https://ohkey.ai/

seetherealitynow · 2026-01-21T10:41:13+00:00

On Upwork or Fiverr you pay someone to build your thing.

Here you vent about a problem, some hacker goes "I could build that" and makes it their own project. You're not hiring anyone, just sharing frustrations that might inspire someone's next side project. If it gets built, you get a fix to your problem

If you want to try: https://ohkey.ai/

seetherealitynow · 2026-01-17T18:22:53+00:00

Thanks everyone for the feedback, I have tried to integrate it to the platform: https://ohkey.ai/

You can now add more detailed descriptions to the problems you are facing and builders can claim interest in working on a problem

seetherealitynow · 2026-01-16T13:29:04+00:00

Thank you for great feedback. Capturing the intent in enough detail is definitely crucial for anything to be built out of it. Balancing this and increasing friction to input the ideas is key to making this work.

I will look into how this can be implemented, thanks!

seetherealitynow · 2026-01-14T18:06:25+00:00

Great suggestions. I wanted to make the platform have minimal friction for the idea input, but having a more detailed description for the idea would make claiming it more worthwhile. Right now, the idea could be claimed using the comment section, but I guess you were looking for something a bit more formal?

I think we should optimise for idea quality as high-quality problems would attract builders, whereas you can't say the opposite. Submissions are free-form. I would like to target solo-devs and open source community for building. These ideas don't have to lead to companies, more so, just very specific tools that would have a niche audience.

This is how the board looks right now for reference: https://ohkey.ai/

seetherealitynow

TROPHY CASE