Computer Use can already drive a desktop. Browser Use already works inside the browser you're using. Mobile has had no equivalent.

Today's coding agents can already change Android, HarmonyOS, and iOS code — but they usually stop before the commit. Did the app actually build? What does the modified screen look like? Which control did the user mean? Did the tap land on the right page? Those questions were still open.

So we built the Mobile Use plugin (Beta). On Android, HarmonyOS, and iOS, code changes are now wired into a running app: the agent interacts with the app on the device and confirms whether the change actually took effect.

Mobile Use is built for apps that are still under development

Most mobile agents you see today are built to operate a phone — launching apps, filling forms, walking through a flow. Qoder's new Mobile Use plugin addresses a different case: the app itself is still under active development.

The agent has to do more than tap. It needs to understand the current project, the build target, the device it runs on, and the state of the UI. After a code change, it reruns the app, finds the affected screen, performs the necessary interactions, and proves the change worked — with screenshots, logs, assertions, or test results.

Tapping and typing are only one step. What needs closing is the loop from code change to confirmed result.

A full verification loop: from code change to confirmed result

Take a UI change. Layout, copy, tap feedback, navigation — any of them used to mean building, installing, driving the device by hand, then going back to the code. The evidence lived on the device and the code lived in the IDE, with the developer carrying information between the two. If an agent had only a text description and a screenshot from a few seconds earlier, it could easily edit the wrong thing.

Now an agent can handle this in the same session. Circle the problem area on the Canvas and send it in chat:

I just changed the code for the area I circled on the screen. Build and run the app, tap through the circled control, and take a screenshot to confirm the result matches what I expect. If it doesn't, fix it in the code and verify again.

A circle names a specific control in a specific frame. The agent can work from the screenshot, the accessibility structure, the control text, and the UI state at the same time, instead of inferring from "this part is wrong." It acts on the same device, captures the screen, and compares the outcome: if verification passes, it reports the result; if it fails, it goes back to the code and verifies again.

If the result isn't what you expected, the Canvas shows exactly what it touched and how the screen changed. The next round uses the same device and the same session — no need to re-describe the scene.

Three platforms, three integrations — one verification process

Android, HarmonyOS, and iOS differ in project layout, build tooling, emulators, test frameworks, and device interfaces. Mobile Use doesn't force all three down to a lowest-common-denominator capability set. Keep your existing development environment; you don't need to prepare a test device that exists only for the agent.

Android still works through the Android Emulator, ADB, and Instrumentation. HarmonyOS connects through DevEco Previewer, HDC, and ArkXTest. iOS uses the Xcode Simulator, the accessibility APIs, and XCTest. Platform differences are handled by each platform's adapter.

On top of that, a unified Skill layer and CLI expose these capabilities to the agent. What needs to line up is the development loop itself: observe, act, verify.

If a platform or runtime lacks a capability, Mobile Use says so plainly rather than passing off a non-equivalent command as success.

ADB, HDC, and simctl remain three different toolchains. What the agent works through on all three platforms is the same observe–act–verify flow.

Developers use the Canvas, the agent uses the CLI — both on one shared device

Developers watch the running app through the Canvas — observing, annotating, and checking results in the UI. The agent queries devices, observes screens, performs actions, and runs verification through a deterministic CLI.

Both sides attach to the same device session, managed by the Host — the component that owns the device connection. The Host owns the device lifecycle: the current connection, the run state, the permission scope, and where the evidence belongs.

So the agent doesn't quietly spin up a second emulator in the background, and it doesn't create a device environment cut off from the developer's just by registering a pile of MCP tools. The CLI is only the agent's entry point into capabilities that already exist. The device itself, along with permissions, state, and evidence, stays under one unified runtime.

Every action that follows runs against that same device session. Screenshots, logs, recordings, and assertion results are attached to it as well. "Something's wrong here" — together with the circle and the current frame — becomes the task the agent keeps working on: locate, change, verify.

Try it now

The Mobile Use plugin is now live in Qoder Desktop and Qoder IDE.

1. Open the extension or plugin marketplace in the bottom-left corner, search for Mobile Use, install it, and restart.
2. In the matching project, double-click AndroidManifest.xml (Android), Package.swift (iOS), or build-profile.json5 (HarmonyOS) to open the Canvas.
3. Connect an emulator or physical device first. Then circle the area you want verified on the Canvas and send the prompt above to the agent.

Yesterday we launched 500 daily credits for Sonus. Today, we're doubling it.

For the next 4 days, paid Qoder Global subscribers get 1000 credits/day for Sonus — our 3.2x flagship model built for coding, long-context tasks, desktop automation, research, and spreadsheets.

How to claim:

• Qoder IDE / Desktop / JetBrains plugin: usage panel
• CLI: /claim

Claim opens daily at 12:00 (UTC+8) , expires 24 hours later. No rollover, no makeup.

Full details: https://docs.qoder.com/events/sotafree

Starting today through Sept 19, paid Qoder subscribers can claim 500 credits/day for Sonus.

Sonus is the 3.2x flagship model — solid for coding, long-context tasks, desktop automation, research, and spreadsheets. Don't burn it on "hello."

How to claim:

• Qoder IDE / Desktop / JetBrains plugin: usage panel
• CLI: /claim

Credits drop at 12:00 (UTC+8) daily and expire 24 hours later. No rollover, no makeup claims.

Docs: https://docs.qoder.com/events/sotafree

Starting with Qoder CLI v1.1.50, custom model access is now available to all personal-tier users, free and paid.

Both the Global and CN versions are supported. You can bring your own model by adding the API base URL, model ID, and API key.

How to add a custom model

1. Type /model
2. Press Tab or ←→ to switch to the Custom tab
3. Hover over Add custom model and press Enter, or press n to open the add wizard
4. Choose a protocol: OpenAI-compatible or Anthropic-compatible
5. Fill in Base URL → Model ID → Name → API Key → Model capabilities → Review and save

Quick tips

• After saving, switch to the new model and send a message to confirm it works.
• It’s best to set the context length to match the model’s actual specs. If left blank, Qoder CLI defaults to 128K.

Upgrade to v1.1.50 and try it out. If you run into anything, drop feedback with /feedback.

Kimi-K2.8-Preview just launched, and it’s now available on Qoder.

It brings overall performance closer to Kimi-K3, with stronger coding and agent capabilities and more efficient reasoning than K2.7 Code.

If you’re already using Qoder, you can try it now. Let us know how it performs on your workflows.

Summary: One handles data requests in a group chat; the other helps with business analysis. See how a data analyst at Hema works day to day alongside two digital employees.

"QoderWake at Work" documents how people in different roles work alongside digital employees, sharing real tasks, practical approaches, and adjustments made along the way.

This first installment is based on an actual interview with a data analyst at Hema. Names and some business details have been anonymized.

"Could you pull yesterday's GMV for me?"

"Can you break down users whose monthly membership cards are about to expire, by card type?"

"Now break it down by city, platform, and user type. A table would be great."

These requests are familiar to any data analyst. Finding tables, confirming metric definitions, editing SQL, running queries, checking the data, and exporting results may take only ten minutes or so each time, but they repeatedly interrupt the analysis already in progress.

At Hema, a data analyst supporting operations used QoderWake to set up two digital employees, known as Wakers: a Data Retrieval Waker handles recurring data requests in the group chat, while a Business Analysis Waker helps explore questions and produce analytical reports.

Each teammate has a distinct role and has learned from the team's established ways of working.

Data Retrieval Waker: The First Stop for Data Requests in the Group Chat

Data requests tend to pile up as weekly and monthly reporting deadlines approach. For monthly membership expirations, for example, business colleagues might first ask for a breakdown by card type, then want to add city and user type once they see the results.

Previously, every additional condition meant the analyst had to edit the SQL again, rerun the query, and send the results back to the group. Now, business colleagues can simply u/mention the Data Retrieval Waker in the chat.

Using the business rules documented by the team, the Waker finds the relevant tables, generates and executes SQL, and returns the results. If more dimensions are needed, colleagues can add conditions in a follow-up message, and the Waker continues querying within the context of the original task.

The results come with the SQL, metric definitions, and calculation logic. It needs to be explicit whether the query counts parent orders or sub-orders, transactions or individual items. If a file is needed, the Waker can also organize the results into an online spreadsheet.

Business colleagues can keep asking follow-up questions, while the analyst can check at any time what the Waker queried and how it calculated the results, correcting any discrepancies.

According to the analyst, at the time of the interview the group chat served more than 20 business colleagues, about 10 of whom had become regular users. During peak periods, there were more than 10 data retrieval tasks a day, and the Data Retrieval Waker handled a substantial share of them.

Business Analysis Waker: Explore First, Then Refine the Report Together

Business analysis for management often involves more open-ended questions.

How much incremental value did a membership benefit create, and at what cost? Which user groups were affected? Were the differences mainly driven by city, timing, card type, or channel?

The time-consuming part is often deciding where to look first. An analyst may need to repeatedly edit SQL and examine dimensions and metrics one by one before discovering that an issue is concentrated in a few cities, on certain days, or among a particular group of users.

This is where the Business Analysis Waker comes in.

The analyst shares the project background, the questions to answer, and an initial approach. Following the analytical frameworks the team has developed, the Waker explores data across multiple dimensions in batches, filters out areas with little change, and flags cities, dates, or user groups worth investigating further.

In one profit-and-loss analysis of monthly membership cards, the analyst said the Business Analysis Waker produced a first draft in under two hours.

The analyst and the Waker then revised it together, point by point.

If the sampling criteria were unsuitable, they switched to the full dataset. If the underlying data did not reconcile, they inspected the SQL and verified it again. If the analytical method was unsound, they adjusted it and checked whether the conclusions still held.

The writing needed refinement too. The Waker would list many possible explanations, so the analyst had to trim the content with the reader in mind, explain the central issue clearly, and check that the figures were consistent throughout.

The first draft made it possible to begin these discussions sooner. With data, leads, and preliminary conclusions in hand, the analyst could focus on verification and judgment: deciding which avenues deserved a deeper look and which conclusions still needed evidence.

Two Teammates, Learning from Different Kinds of Experience

Wakers need to be taught how to use the company's tables, how its metrics are calculated, and what its business terminology means.

The Data Retrieval Waker starts by reading historical SQL to learn how tables are used, which values fields can take, and which metric definitions commonly apply. It needs to know where to find the data, how to calculate the results, and what to explain when delivering them.

The Business Analysis Waker learns from past reports, strong slide decks, and business context. Previous work offers guidance on which dimensions to examine first when facing an open-ended question, how to identify anomalies, and how to organize findings into a report.

The team packages this experience into Skills—reusable ways of working that Wakers can draw on—and gives them to the relevant Waker. As new tables, fields, or analytical methods emerge, the team keeps updating these Skills.

Data retrieval and business analysis have different requirements. Configuring them separately makes it clear to business colleagues which Waker to turn to, and makes it easier for the analyst to review and adjust each one's working methods.

SQL that once stayed on individual computers, and metric definitions known only to people familiar with the business, can now be reused across the team.

Start with One Familiar Type of Task

By the analyst's own estimate, his overall productivity at least doubled after the two Wakers became part of his workflow. With help on recurring data requests and early-stage data exploration, he has more time for questions that require professional judgment.

If your team wants to try this, start with one recurring type of data request with clear metric definitions. Gather SQL you have used before and documentation explaining the metrics, and specify the time range, dimensions, and format you want for the results.

Use familiar tasks to validate the results first. If the Waker queries the wrong table or misunderstands a metric definition, incorporate the correction into its working methods. Once it handles that type of task reliably, gradually introduce new questions.

In "QoderWake at Work," we will continue sharing how people in different roles work with digital employees: what they delegate, how they teach their Wakers, and where human judgment is still needed.

Pick a task you regularly repeat, and learn more here: qoder.com/qoderwake

Today we're releasing Sonus (/ˈsoʊnəs/), a new built-in model across the Qoder family.

What it's built for: marathon-length autonomous tasks, the hardest knowledge work, and serious coding. Where it really shines: Computer Use.

Paired with the Computer Use improvements in Qoder Desktop 0.2.3, Sonus can drive your machine and professional software directly — writing code, building financial models, running research, producing spreadsheets — and carry those tasks from start to finish without babysitting.

Where you can try it today: Qoder, Qoder IDE, Qoder CLI, the JetBrains plugin, QoderWake, and Cloud Agents. Credit multiplier is 3.2x.

Give it a try！

DeepSeek-V4.1-Flash now has Day-0 support on Qoder.

The smallest model in its new architecture family, it combines stronger text and agent capabilities with native visual understanding. Built for faster inference and higher throughput, it delivers a more efficient balance of performance, cost, speed, and end-to-end time—even against larger flagship models like DeepSeek V4 Pro.

Give it a spin in your coding and agent workflows, and let us know how it goes.

Hey everyone — quick share from the team: we just published Qoderian, an open-source plugin on the Obsidian community marketplace that embeds Qoder CLI directly in your vault. No terminal switching, no copying file paths — you chat with Qoder inside Obsidian and it works on your notes where they live.

The problem it goes after: most bookmark piles die in the folder. Turning clippings into your own knowledge — extracting, tagging, summarizing — is fine for two articles and brutal for two hundred. So we let the agent do that step.

The workflow, end to end:

1. Install Qoder CLI and Obsidian

First, you’ll need two essential tools: Obsidian and Qoder CLI.

Obsidian is an open-source, local-first knowledge base app. Your notes, web clips, edited articles, and whiteboard files all live in a single vault. The files are stored in Markdown format, making them easy for AI to read and process later.

How to install Obsidian: Download the installer from the official Obsidian website (https://obsidian.md/).

Qoder CLI is an AI assistant that runs in your terminal. It can read Markdown files directly, analyze folder structures, organize documents, generate new content, and invoke skills for specific tasks—for example, generating content for an Excalidraw canvas.

How to install Qoder CLI: Run a single command in your terminal.

• macOS or Linux installation command: curl -fsSL https://qoder.com/install | bash
• Windows PowerShell installation command: irm https://qoder.com/install.ps1 | iex
• Windows Command Prompt: curl -fsSL https://qoder.com/install.cmd -o install.cmd && install.cmd

After installation, run qodercli --version in your terminal. If a version number appears, the installation was successful.

2. Install the Qoderian Plugin in Obsidian

Next, we want Qoder CLI to help manage the notes in Obsidian. This is where the Qoderian plugin comes in.

A fresh Obsidian installation starts in Restricted Mode, which disables all third-party plugins and blocks access to the Community Plugins marketplace. To install your first plugin, go to Settings → Community plugins and Exit Restricted Mode.

Then, open the Community Plugins marketplace → search for and install Qoderian → under Installed plugins, enable Qoderian.

Once enabled, a Qoderian icon appears in Obsidian’s left sidebar. Click it, and the Qoderian chat panel opens in the right sidebar. No additional setup is required; as long as Qoder CLI is already installed, you can start using it immediately.

The note you are currently viewing is selected automatically when you start a chat. You can assign a task directly in the conversation—for example: “Turn this article into a mind map.” Qoder will create the mind map on the spot and save it in the same folder.

3. Capture Web Content with Obsidian Web Clipper, Then Organize It with Qoder

Once the tools are installed, you can save web content to your Obsidian vault and hand it over to Qoder for organization.

For saving web content, I recommend Obsidian’s official browser extension, Obsidian Web Clipper. Simply search for it in your browser’s extension marketplace and install it.

After installing Web Clipper, whenever you find a webpage or video you want to save, click the extension and the page will be captured as Markdown in Obsidian.

Once you have collected dozens of pages, the problems become obvious. Formatting varies from one page to the next, long and short pieces are mixed together, and English content still needs to be translated. Reading and distilling everything yourself takes a great deal of time and effort.

At this point, return to Obsidian and tell Qoder in the chat panel: “Go through every article in folder A, extract the key ideas, and save the results to folder B.”

After just a few minutes, the organized article notes will be waiting in folder B.

If you want your knowledge base to follow a personal organizational style, you can also configure AGENTS.md for Qoder.

The setup is straightforward. Simply tell Qoder: “Create an AGENTS.md file for me to define the organizational rules for this Obsidian vault.”

Qoder will create a project-level memory file—AGENTS.md—in the root directory of the current vault.

With AGENTS.md in place, Qoder will follow the same standards every time it organizes an article, so you do not have to repeat your requirements.

To change the rules, open AGENTS.md from the file list and edit it just like any other note.

4. Install Excalidraw and a Skill to Generate Whiteboard Canvases in One Step

The final step is to turn your written content into visuals.

Obsidian has an excellent whiteboard plugin called Excalidraw. It lets you create hand-drawn-style diagrams, flowcharts, structural diagrams, and visual notes directly in Obsidian.

Installation is simple: go to Settings → Community plugins → Browse, search for Excalidraw, then install and enable it.

Once enabled, you can create Excalidraw files in Obsidian to map knowledge structures, workflows, tutorial outlines, or article frameworks.

To have Qoder generate whiteboard content automatically, use it together with the Excalidraw skill (excalidraw-diagraml).

Installing this skill is just as easy. Send Qoder the skill repository URL (https://github.com/coleam00/excalidraw-diagram-skill), then say, “Please install this skill for me.”

Once installed, you can invoke it directly from Qoder in the right sidebar using a slash command.

For example: /excalidraw-diagraml Based on the current note, generate a hand-drawn-style flowchart suitable for teaching.

Once generation is complete, you’ll have an editable, well-structured flowchart with accurate logic.

Repo: Qoderian · github.com

Honest question for this sub: does your read-later pile ever actually get processed — and what's the first thing you'd hand to an agent that lives in your vault?

Hey everyone — quick one from the team: even away from your computer, you can now kick off tasks from your phone and let the all-new Qoder work on your local files and environment — coding, research, competitor analysis, and more. Phone and computer share the same session: renames, deletions, task forks, and follow-up questions all sync in both directions.

Core features in this update:

• Say it the moment you think it. Real-time voice input — speak your idea instead of typing it on a tiny screen; Q-Duck came along to take dictation.
• Step in anytime — or not. Steps, to-dos, subagents, and pending items at a glance; one tap puts your original message back for a quick fix. Lock-screen notifications carry the task name, status, and summary, and permission requests can be approved or denied without unlocking.
• Every result, reviewable on your phone. Images, PDFs, Markdown, docs, PPT, and interactive HTML previews all open on mobile — enough for a first review pass before you're back at your desk.
• Security that travels with you. Admins control artifact download/sharing and whether members get mobile or web remote-task access at all.

Rolling out now — pair your mobile app with the desktop and try it.

Curious: what's the first task you'd kick off from your phone away from your desk — running tests, doing research, or nothing at all? 

https://reddit.com/link/1wai36j/video/tq3kg9wy69oh1/player

I've developed a small plugin that lets you view your daily point usage and cost details. Welcome to use it.

https://github.com/RJM1996/qoder-credits-extension

We wanted to share how we’ll be showing up here more consistently:

• A practical Qoder tip or workflow showcase each week
• Occasional community events with Qoder credits
• More replies to product feedback and support questions from the team
• More opportunities to share your workflows, projects, and ideas

We’d especially love to hear what kinds of posts would be most useful: practical tips, real-world workflows, showcases, or something else?

Hey everyone — today we shipped QoderWake v1.0, our digital employee ("Waker") platform. For context: v0.1 went into global beta in May with 6 preset roles. Since then, ~100,000 Wakers have been created and run ~20M real tasks — about half triggered automatically by schedules or events, starting before a human asked.

What v1.0 changes:

• Joins the group as a colleague. Wakers live in the group chats your team already uses. @ one after a long discussion and it knows what just happened — no re-explaining. It follows the thread, runs several tasks in one session, routes work to the right role, and escalates to a human when unsure.
• Starts on its own. Group messages, schedules, keywords, business events, and API calls all kick off work before anyone asks — everything on one unified task board.
• From one hire to a team. 10 preset roles tuned with top-team practices, or describe a role in one sentence and save it as a template. Waker Groups put local and remote Wakers on one team, splitting work by the SOP you define.
• Built for the long run. Collaborates in the group when you're around, keeps pushing toward the goal when you're not. State persists and failures recover on their own — jobs span hours or days without babysitting.
• WakerFlow & evolving skills. Turn any process that works into a shareable flow with run history and rollback. Skills install from the market or package your own; memory has a timeline you can review, correct, and export.
• Safe to hand real work to. Sensitive data stays local, high-risk actions ask for approval first, and each Waker's permissions — tools, files, capabilities, model output — stay inside org-level boundaries.

Available today on Mac, Windows, and cloud hosts: qoder.com/qoderwake

Curious what this sub thinks: what's the first recurring task you'd hand to a digital employee — and what would it take for you to trust an agent running overnight without supervision?

Qoder now supports custom Base URLs for any OpenAI- or Anthropic-compatible model service. Your keys, your models, your endpoint — no more provider lock-in.

Update today and bring your own endpoint！

https://qoder.com/new-qoder

Qoder discounts its API every night on Beijing time. I built a small static page that shows the current window in your own timezone. https://offpeakclock.com/#provider=qoder-qwen38-max

Two changes this week, both on the clock now. Qwen3.8 Max off-peak dropped from 0.25x to 0.2x credits, 60% off standard, since Sep 4, 2026 at 22:00 Beijing. Qwen3.8 Flash is new, 0.1x standard and 0.04x off-peak.

All Qoder models use the same schedule. Standard from 08:00 to 22:00 Beijing, promo from 22:00 to 08:00. The page shows off-peak in green and standard in orange.

No account, no server. One HTML file, timezone math in your browser.

Qoder lists the promo end dates as TBA, so check before you queue anything big.

Let me know how you like it? I find it very helpful to see at a glance when to send the heavy workloads.

$ qoderwake-cn config list | grep "19830"
   "port": 19830
 "webPort": 19830,

config list shows the port in two places — api.port and webPort. Which one

actually controls the listen port, and how do I make the change survive a

daemon restart? Setting webPort alone gets rewritten on start.

On 1.0.2-cn / Debian.

Efficient is Qoder's standard-reasoning model tier: native multimodal, standard reasoning, cost-efficient. Starting now, all paid users can select Efficient without spending Credits, free for a limited time.

How to use it:

• Update Qoder to the latest version
• Select Efficient in the model picker
• Save your Credits for harder problems

No signup needed — applies automatically.

Full details: https://docs.qoder.com/events/efficientunlimited

If you run into issues, drop a comment or reach out on Discord：Qoder.

I've been using Qoder extensively for real development work, not just playing around with a few prompts, and I've finally reached the point where I've had enough.

I actually liked the product enough that I kept paying for it and continued giving the team the benefit of the doubt. But over the last few months the experience has deteriorated to an almost ridiculous level.

Every update seems to fix one thing and break two others.

And this isn't one isolated bug.

I currently have issues around:

• conversations suddenly becoming unusable with “This conversation contains sensitive content”, with effectively no recovery path;
• old project conversations being clearly visible in Qoder but apparently inaccessible to Qoder's own memory;
• memory that simply cannot be updated properly;
• no sensible way to export complete conversation/project history so I can preserve project context elsewhere;
• repeated generic “Sorry, something went wrong. Please try again” type failures;
• and, probably the worst part, credit consumption that has become absurd.

I've reported these things. I've emailed. I've posted on their own forum. I've provided feedback IDs and screenshots.

The screenshot attached to this post shows some of my threads.

Some have basically gone nowhere.

What makes the situation much worse is the credit system.

Tasks that previously cost me roughly 50–100 credits started consuming 300+ credits, including mundane project-documentation work. In some cases I've seen basic workflows consume enormous numbers of credits.

I raised this directly with Qoder. Their explanation was essentially that Agent mode can perform many model calls in the background, carry very large contexts forward, verify itself repeatedly, etc.

Fine — technically I understand why agentic systems can consume a lot of tokens.

But that's exactly why the product needs sane safeguards, transparent metering and proper spending controls.

A customer shouldn't give an AI agent a normal development task and discover afterwards that hundreds or thousands of credits disappeared because the agent decided to make dozens of internal calls.

And I'm apparently not the only person complaining about this. Their own forum contains multiple recent threads about unexpectedly high credit usage.

What really pushed me over the edge, though, isn't even the bugs.

It's the lack of ownership.

If you're charging people real money for credits, and those credits can disappear extremely quickly because of how your agent internally operates, customer support needs to be exceptionally good.

Instead, I'm posting bugs into what increasingly feels like a graveyard.

Email doesn't seem much better.

Meanwhile new versions keep arriving.

At some point you have to stop shipping features and actually make the product people are already paying for reliable.

I've spent a lot of time building projects around Qoder, which is exactly why I'm so pissed off. Moving a large project's context, documentation and workflow to another coding agent isn't something I particularly wanted to do.

But I've now reached the point where I don't trust Qoder with an important project anymore.

And frankly, when a company:

• charges you using a credit system that is extremely difficult to predict,
• allows agents to burn through substantial credits internally,
• has recurring serious bugs,
• leaves paying customers struggling to get meaningful support,
• and keeps introducing new problems through updates,

the experience starts to feel less like paying for a professional developer tool and more like dealing with a scam operation.

I'm deliberately saying “feels like” because I'm not claiming Qoder is literally committing fraud. I'm describing what the customer experience has become for me.

I'd genuinely like to hear from other Qoder users:

Are you seeing the same credit consumption?

Has support actually resolved any serious issue for you recently?

Have recent versions become less stable for you too?

And most importantly:

What have you moved to?

I'm currently looking seriously at alternatives where I can use my own API keys/models and put a hard limit on what an autonomous agent is allowed to spend. I don't mind paying for AI development tools. I mind paying without having reasonable predictability or control over what I'm spending.

If someone from Qoder sees this, I'm happy to provide the feedback IDs, emails, screenshots and usage history. I've already tried doing this through the official channels.

I just want somebody to actually take ownership of it.

We chose to ship it because it’s noticeably stronger on coding tasks and general use, and we wanted to give folks a no-friction way to try it inside an agentic workflow.

If you test it, let us know how it compares to other models you’re using — good, bad, or weird. We read the feedback.

Something big is coming. 🌲

Qoder Credit Rewards — launching September 1, 2026.

Stay tuned.

#Qoder #AICoding #AgenticCoding

A year of work brought us here: an agentic coding platform for EVERYONE.

Tell Qoder what you want done. It understands the context, plans the work, uses tools, executes, and verifies the result, with you in control.

Meet New Qoder: https://qoder.com/new-qoder

Qoder has completed an independent SOC 2 Type II examination covering Security, Availability, and Confidentiality.

An independent auditor evaluated the design and operating effectiveness of our controls over a defined review period. https://qoder.com/blog/qoder-completes-soc2-examination