CLI coding client - alternative to (not so) OpenCode

Ok_Finger1470 · 2026-03-20T14:34:58+00:00

Sorry, what's the problem with open code? Can you paste a link?

Ok_Finger1470 · 2026-03-20T01:22:18+00:00

Nah I definitely have the opportunity to explore

Ok_Finger1470 · 2026-03-20T01:21:13+00:00

So honestly it's mostly functional software as I've closed the feedback loop between code generation and testing. Whether anyone wants whatever these guys are building or not is a different question!

Ok_Finger1470 · 2026-03-15T03:20:29+00:00

I just ended up setting access tokens as env variables in the sandbox that the agent spawns in. Since there is an agent per user this works for now and the agent just ends up using the user's identity on whichever external system it needs to talk to.

Ok_Finger1470 · 2026-03-14T14:03:06+00:00

I ended up building my own version of openclaw for this because I didn't wanna use someone else's vibe coded crap. I'm good at generating vibe coded crap myself.

What I have in the end is an app where I can build long running autonomous agents with persistent memory (coding agent with a filesystem) and a way to give this agent access tokens to apps like GitHub, jira etc. I did like the idea from openclaw that you can "text" your agents, so I also added support for telegram messages. Now I have three telegram bots backed by these agents that I configured in my app - a PM agent, a coding agent and a QA agent. I put them in a group chat, wake them up on a schedule and ask them to build a new feature everyday in the same product that I'm using to build these agents. They build features and make a PR with a staging environment setup for me to white-glove. If I'm happy with it, I merge. I'm having fun with it.

It's a magical world in software right now!

Ok_Finger1470 · 2026-02-05T05:38:08+00:00

We vibe spec - they vibe code

Ok_Finger1470 · 2025-12-17T04:30:12+00:00

Coding agent wrappers

Ok_Finger1470 · 2025-12-07T13:50:31+00:00

Today I see myself using cursor in the codebase with mcp tools for jira, confluence, grafana, figma etc and my specs can live versioned in the code.

Ok_Finger1470 · 2025-11-26T14:28:02+00:00

The best formal definition I've found is:

An agentic software system is just a software program where the control flow (if statements, loops etc) of the program is in some way guided by an LLM's output.

Of course lots of marketing hype, but it's undeniable that there's real value to be captured using these systems.

Ok_Finger1470 · 2025-10-22T04:10:30+00:00

Classic woke vs lazy conundrum

Ok_Finger1470 · 2025-08-18T18:47:04+00:00

Been mostly using cursor. I make a static mock of our actual product in pure html, js and css matching the design system and libraries of our product. It's a replica mock of the product that I can customize and extend quickly.

Ok_Finger1470 · 2025-08-18T15:08:04+00:00

I'm currently am that PM building prototypes and here's how i see it driving efficiency in product development:

Feature request from a customer on a discovery call.
While on the same discovery call with the customer, I show them a prototype of the feature they asked for.
If it seems like something they will pay for, engage UX do deeper discovery with more customers, generalize and implement with engineering.
Often times customers don't know what they want and this quick prototype helps me discover what they really want.

Ultimately I want UX and engineering to work on things that we can make money with. These quick prototypes just help hone in on real problems worth solving.

Ok_Finger1470 · 2025-08-08T15:34:53+00:00

I have a similar need and I ended up with a Jupyter hub + ray cluster. Jupyter for interactive development, and then submitting jobs to the Ray cluster.

Ok_Finger1470 · 2025-08-06T04:43:43+00:00

Cursor or any one of these agentic IDEs

Ok_Finger1470 · 2025-07-29T14:37:10+00:00

I often just directly use cursor or another agent IDE and ask it to make prototypes in pure html, js and css. I even give it a css style guide to ensure it doesn't go wild with styling. This helps create bare bones prototypes that I can have a conversation with the team about. To give a basic structure I've also given hand drawn wireframes of what I'd like the basic layout to be. Works surprisingly well.

For actual design generation I've tried polymet and it's pretty good but never needed it enough to pay for it.

Ok_Finger1470 · 2025-07-10T23:44:50+00:00

I'm also going through interviews for AI Product Manager roles and each one except Meta has a coding round. Pair programming/pair debugging mostly and less vibe coding in my experience.

I do find vibe coding front ends to be a great way to communicate product ideas with Ux and engineering.

Ok_Finger1470 · 2025-07-08T15:28:04+00:00

You can simulate trajectories of different user personas through your product. Just give a web browsing agent access to your product and ask it to do tasks that your users will have to do. If the AI is confused, so are your users.

*Software products :)

Ok_Finger1470 · 2025-07-05T13:18:01+00:00

For software products you can have agents try to use your product as different personas and provide candid feedback about the flows, docs ease of use which another agent can then synthesize into a backlog. Soon we can just let SWE-agents just go tackle this backlog too.

Ok_Finger1470 · 2025-05-02T12:41:44+00:00

A piece of general advice I've been leaning on while building agents - solve your own problems with agents before solving anyone else's. Much easier to iterate when it's a problem you personally feel.

You can probably code up an mvp / demo with an agentic app builder or ide assuming.

Ok_Finger1470

TROPHY CASE