DEV Community: Cüneyt Çakar

A UI Task Is Not Done When the Agent Says It Is

Cüneyt Çakar — Tue, 27 Oct 2026 20:38:07 +0000

A coding agent can produce a plausible UI change and still miss the behavior a person sees. That gap is one of the problems I am exploring while building Spexop UI.

A small example

Imagine a task: add a settings control and explain its state clearly. A useful check might include three layers:

Deterministic checks: Does the code build, and do focused tests cover the intended state change?
Browser observation: At the exact revision under review, can a real browser reach the control, operate it, and display the expected state on the relevant screen sizes?
Human decision: Does the behavior actually meet the product intent and fit the user’s workflow?

Passing one layer does not silently pass the next. A test double can exercise coordination logic, but it cannot prove that a live provider API works. A screenshot can show one browser state, but it cannot prove every interaction. A successful implementation does not grant product acceptance.

What Spexop is aiming to coordinate

The intended Spexop UI companion will keep the developer’s existing coding agent responsible for planning, design, risk, and oversight. Bounded, user-connected API workers would handle routine UI tasks. Spexop would track a minimal milestone, gate, and task flow; attach checks to the revision being evaluated; and show progress, blocked, or needs-user-action in plain language.

Today the evidence is narrower: a private local coordination prototype with test doubles and a loopback browser status view. There is no packaged desktop app or verified live provider worker, and external product acceptance is still open.

I am interested in the boundary between automated evidence and a human go/no-go decision. For a small UI task in your project, which browser behavior would you insist on checking before you trusted a worker’s result?

Current Spexop direction and status · Product overview

What Spexop UI Is Building — and What Exists Today

Cüneyt Çakar — Tue, 27 Oct 2026 20:37:22 +0000

Spexop UI is an early, free, local-first, open-source UI/UX desktop companion in development. I am sharing the direction and the current evidence separately so readers can tell what exists today from what we still intend to build.

The intended workflow

A developer keeps their existing strong coding agent in charge of planning, design decisions, risk, and oversight. User-configured free or low-cost LLM API workers are intended to take on bounded routine UI tasks. Spexop coordinates a small milestone, gates, and tasks in the background. It should verify each result with deterministic checks and a real browser when the task needs one, then show plain progress, blocked, and needs-user-action states.

The goal is to make small UI changes easier to delegate and inspect without losing the developer’s control of the project.

What we have actually checked

Current evidence is a private local coordination prototype that uses test doubles, plus a loopback browser status view. The prototype has technical tests and a real-browser observation of the local status flow. Those results support only that narrow prototype.

There is no packaged native desktop app, no verified live LLM API worker, and no external product acceptance yet. The Groq access path remains blocked by a provider-side 403 response. The public-source review is still open, so the current monorepo is not being presented as a public release. Earlier Theme, Foundation, Capture, and icon work are technical assets, not evidence that this new companion is ready to install.

Where to follow and contribute

The current product direction and status are on spexop.com. You can also follow the Spexop UI LinkedIn page.

I would value feedback on one question: what is the smallest UI task you would trust a bounded worker to do if a coding agent planned it and independent checks reported the result?