MKNOWN ISSUES

A clear view of known issues.

A place to see an issue’s status and impact in one place.

The live issue feed is not connected.

This does not mean the product has no issues. Only confirmed records tied to actual versions should be published here.

What an issue record should show

Affected version and task

When the problem can occur

Current status

Investigating, preparing a fix or released

What you can do now

Verified workarounds and update guidance

프로젝트 이어가기

Archived September 9, 2026 · Actual app with example data

WHY I BUILT MINDSTRUO

I wanted to build a small app. I ended up building a way to keep going.

In early 2026, ChatGPT and Gemini made me curious about what I could build. I was impressed, but longer, more complicated work still felt difficult. After hearing about vibe coding on YouTube, I wanted to try making a calendar app or a small game.

I barely knew where to start. I pasted AI-generated code into development tools and brought the errors back to the chat. Getting something to run took time. Getting it to run didn't mean it worked well.

I later experimented with more autonomous coding setups, including OpenHands. A different problem became clearer: I kept explaining past decisions, failed approaches, and unfinished work. I started exploring how that context could carry into the next task.

For a while, the coding models in my setup still felt like the larger bottleneck, and I stepped back. Codex was the turning point for me. I found it easier to finish real tasks, so I returned to those earlier experiments and developed them around a Codex workflow.

I didn't want starting the next conversation to mean rebuilding the whole project.

That work became MindStruo. Using it made the connection between decisions, evidence, reviewed results, and next steps increasingly clear. There is still a lot I want to improve and build on this foundation.

Now I want to know whether it helps people who work differently from me. That's why I want to hear about the useful moments, the frustrating ones, and the experience that didn't match what you expected.

MAKE MINDSTRUO MORE USEFUL

사용 경험을 들려주세요.

One concrete experience is enough.

Your message is not stored on a server or sent automatically. Review it in your email app before sending. Do not include passwords, API keys, or sensitive source content.