HOW I GUIDED THE WORK
Keeping the project
on the right track
I described what I wanted, followed the work as it happened, and corrected it when it drifted. These are three decisions I pushed for while building Mojow with AI.
The decisions below come from my requests during development. The implementation and verification summaries come from the dated project records.
01 / SIMPLIFYING THE EXPERIENCE
One conversation
for the work
Implementation recorded October 22, 2026.
Installed acceptance recorded October 23.
What I noticed
The app separated ordinary chat from work on files. I questioned why there were two modes and wanted to use one conversation for both.
The direction I gave
Let me ask a question, then ask for a change, without having to choose a different mode first. Keep the conversation together.
What the implementation changed
The separate Chat and Build selector was removed. One composer now routes questions and explicit supported change requests through the existing conversation workflow. The guarded runner still controls file changes and build/test work.
The October 23 installed API acceptance records an answer, a read/hash/edit/build/test request, Stop behavior, and saved-thread continuity after a Launcher restart.
This is a dated acceptance record. The portfolio session did not rerun those product checks.
02 / MAKING THE APP UNDERSTANDABLE
Names I can
recognize
Naming release recorded October 23, 2026.
What I noticed
The connection list was full of generic labels and short identifiers. It was difficult to tell which entry was which, so I asked for meaningful names.
The direction I gave
Give these entries names that help me tell them apart, with their workspace visible.
What the implementation changed
Connections show a readable title with workspace and client context underneath. Manual names take priority. When the purpose is unknown, the app uses a fallback instead of guessing. Renaming a connection keeps its existing identity.
Unassigned / Untitled chat / a1b2c3
Portfolio workspaceMojow Connector / MCP client
The release records installed naming preferences and automated checks for the production rows and headings, including duplicate-name cases.
A post-install inspection of the live Connections page was not captured. The portfolio screenshot was made separately with sample data.
03 / CHOOSING HOW CONTROL SHOULD WORK
Control through
an API
Local chat and shared app-control records:
October 23, 2026.
What I asked for
I wanted AI to control Mojow without taking over the screen. I specifically asked for an API-only approach.
The direction I gave
Let AI control Mojow through an API without taking over the screen.
What the implementation changed
A local API connects to the existing chat workflow through a named pipe for the same Windows user. Requests identify their target and keep saved results. Stop applies to the requested run. The later shared command system adds state, project, and chat controls.
The records describe installed question, edit, Stop, and continuity checks. The first shared command release covers 12 commands, with recorded API and native AI rename/select cases and stale or duplicate request handling.
Full shared AI control is still in progress. This does not mean that every control in the application is available through the new API.
A SMALL FIRST PROJECT
How I'd approach
freelance work
This is how I'd like to work with someone remotely. Mojow is my personal project and the example behind this approach.
- 01
Agree on the useful part
Describe the problem, who will use the tool, and one task it should handle. Write down what is outside the first version.
- 02
Build something you can try
Use AI to help implement a small version. Follow the progress, review the result, and correct the direction when needed.
- 03
Check the result together
Try the agreed task with sample data. Keep track of what works, what failed, and what still needs attention.
- 04
Leave a clear handoff
Provide the files, setup steps, known limitations, and a short explanation of how to use the result.
I'm interested in remote freelance work involving small tools and workflow prototypes. The first conversation would be about your problem and whether it fits the work I can take on.
BASIS FOR THESE EXAMPLES
Development requests and project records reviewed October 24, 2026. Summaries are paraphrased; private conversations and raw execution receipts are not reproduced here.
- Unified conversation implementation, October 22, 2026.
- Local chat API and friendly connection names, October 23, 2026.
- Shared AI app-control core, October 23, 2026.
The technical implementation was done with AI. My contribution was the design, direction, detailed prompts, and ongoing review described above.