<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Magshifter</title>
    <description>The latest articles on DEV Community by Magshifter (@magshifter).</description>
    <link>https://dev.to/magshifter</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4207226%2F11416af1-6c4a-452c-867b-8a5517090777.jpg</url>
      <title>DEV Community: Magshifter</title>
      <link>https://dev.to/magshifter</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/magshifter"/>
    <language>en</language>
    <item>
      <title>Cursor Changed — and My First Account Merge Went Very Wrong</title>
      <dc:creator>Magshifter</dc:creator>
      <pubDate>Mon, 16 Nov 2026 14:35:33 +0000</pubDate>
      <link>https://dev.to/magshifter/cursor-changed-and-my-first-account-merge-went-very-wrong-4mjg</link>
      <guid>https://dev.to/magshifter/cursor-changed-and-my-first-account-merge-went-very-wrong-4mjg</guid>
      <description>&lt;p&gt;I didn’t set out to migrate my Cursor subscription.&lt;/p&gt;

&lt;p&gt;I didn’t even plan to change anything about my development setup.&lt;/p&gt;

&lt;p&gt;This whole story started because I wanted to install &lt;strong&gt;Grok Bot on my phone&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Instead of opening the account I was already using, the mobile flow ended up creating or selecting another account under the same email. Suddenly, Cursor, Grok, and Grok Bot were no longer where I expected them to be.&lt;/p&gt;

&lt;p&gt;So I contacted support.&lt;/p&gt;

&lt;p&gt;That was the moment a small account issue turned into a much bigger billing problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  Nine days earlier, I had bought Cursor Ultra
&lt;/h2&gt;

&lt;p&gt;On November 7, 2026, I purchased Cursor Ultra through a discounted offer.&lt;/p&gt;

&lt;p&gt;The normal price was around $200, while I paid roughly $100.&lt;/p&gt;

&lt;p&gt;For the way I use Cursor, that was a very good deal.&lt;/p&gt;

&lt;p&gt;Cursor had already become one of my main coding executors. I use AI heavily for implementation, debugging, repository work, testing, and longer development sessions, so the larger Ultra allowance wasn’t something I bought “just in case.”&lt;/p&gt;

&lt;p&gt;I actually needed it.&lt;/p&gt;

&lt;p&gt;When the duplicate-account problem appeared after installing Grok Bot on my phone, my goal was simple: fix the account situation &lt;strong&gt;without losing the Ultra subscription I had just paid for&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Support told me to merge the accounts
&lt;/h2&gt;

&lt;p&gt;The first support agent I spoke with was an xAI AI-support agent named Sam.&lt;/p&gt;

&lt;p&gt;I explained the situation and was directed to use the account merge flow.&lt;/p&gt;

&lt;p&gt;The reassurance I received was very clear:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;“Nothing has been lost.”&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;So I followed the support instructions.&lt;/p&gt;

&lt;p&gt;After the merge, my Cursor Ultra subscription was gone.&lt;/p&gt;

&lt;p&gt;I received a refund of &lt;strong&gt;$70.19&lt;/strong&gt;, and the merge itself turned out to be permanent.&lt;/p&gt;

&lt;p&gt;At that point, this was no longer a simple sign-in problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cursor and Grok are now part of a much closer subscription system
&lt;/h2&gt;

&lt;p&gt;On &lt;strong&gt;October 12, 2026&lt;/strong&gt;, xAI announced &lt;strong&gt;The X Subscription&lt;/strong&gt;, bringing Grok, Grok Bot, Cursor, and X Premium into a shared subscription ecosystem.&lt;/p&gt;

&lt;p&gt;The concept itself makes sense.&lt;/p&gt;

&lt;p&gt;One account, one subscription, and shared access across several AI products can be much simpler than maintaining separate accounts and bills.&lt;/p&gt;

&lt;p&gt;But existing Cursor users are not starting from zero.&lt;/p&gt;

&lt;p&gt;They may already have old plans, annual subscriptions, promotional pricing, multiple accounts, or separate Grok and Cursor identities.&lt;/p&gt;

&lt;p&gt;That makes migration much more sensitive than creating a brand-new account.&lt;/p&gt;

&lt;p&gt;And apparently I wasn’t the first person to discover that.&lt;/p&gt;

&lt;h2&gt;
  
  
  I found the previous reports too late
&lt;/h2&gt;

&lt;p&gt;Only after my own merge did I start searching the Cursor forum for similar cases.&lt;/p&gt;

&lt;p&gt;There were already users reporting account-unification problems in late October.&lt;/p&gt;

&lt;p&gt;Some described Grok Bots ending up on one account while the paid plan was attached to another. Others reported that parts of their previous account state were no longer available where they expected them after unification.&lt;/p&gt;

&lt;p&gt;By October 27, Cursor staff had publicly acknowledged problems affecting some account migrations.&lt;/p&gt;

&lt;p&gt;That was the frustrating part for me.&lt;/p&gt;

&lt;p&gt;The problem wasn’t completely new by the time I encountered it.&lt;/p&gt;

&lt;p&gt;I simply learned about those precedents &lt;strong&gt;after&lt;/strong&gt; completing an operation that cannot be reversed.&lt;/p&gt;

&lt;h2&gt;
  
  
  The official documentation makes my case even more confusing
&lt;/h2&gt;

&lt;p&gt;The current documentation makes an important distinction between several actions: signing in, linking accounts, collapsing multiple Cursor accounts, and switching plans.&lt;/p&gt;

&lt;p&gt;According to the documentation, &lt;strong&gt;account collapse by itself does not switch your plan or cancel an existing subscription&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Subscription changes are supposed to happen separately as part of an eligible checkout when switching to The X Subscription.&lt;/p&gt;

&lt;p&gt;The same documentation also says completed unification is permanent and cannot be undone by support.&lt;/p&gt;

&lt;p&gt;That combination is exactly why I have now escalated the case to billing.&lt;/p&gt;

&lt;p&gt;I don’t want to speculate about which internal step caused my Ultra plan to disappear. That is something the billing team needs to investigate.&lt;/p&gt;

&lt;p&gt;From my side, the sequence is much simpler:&lt;/p&gt;

&lt;p&gt;I had an active Ultra plan.&lt;/p&gt;

&lt;p&gt;I had an account problem after trying to use Grok Bot on mobile.&lt;/p&gt;

&lt;p&gt;Support recommended a merge.&lt;/p&gt;

&lt;p&gt;I followed the instructions.&lt;/p&gt;

&lt;p&gt;Ultra disappeared.&lt;/p&gt;

&lt;h2&gt;
  
  
  The $70.19 refund did not put me back where I started
&lt;/h2&gt;

&lt;p&gt;The refund also needs some context.&lt;/p&gt;

&lt;p&gt;xAI’s documentation explains that when an old subscription is cancelled during a plan switch, the unused part of the billing period can be refunded on a prorated basis.&lt;/p&gt;

&lt;p&gt;That appears to be what the $70.19 represents.&lt;/p&gt;

&lt;p&gt;So this is not really compensation for losing a discounted Ultra plan.&lt;/p&gt;

&lt;p&gt;It is closer to a refund for the unused days of the subscription.&lt;/p&gt;

&lt;p&gt;The difference matters because I paid roughly $100 for Ultra under a promotional price.&lt;/p&gt;

&lt;p&gt;Getting $70.19 back does not give me the ability to simply purchase the same plan again under the same conditions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Premium feels very different for my workload
&lt;/h2&gt;

&lt;p&gt;Right now, the plan I still have is Premium purchased through Apple.&lt;/p&gt;

&lt;p&gt;It remains active until December 15, with renewal disabled and no additional prepaid credits.&lt;/p&gt;

&lt;p&gt;Under the new model, Grok, Grok Bot, and supported Grok usage in Cursor share a weekly usage pool. Third-party models such as Claude or GPT inside Cursor require separate credits.&lt;/p&gt;

&lt;p&gt;For a light user, that may be completely fine.&lt;/p&gt;

&lt;p&gt;For my development workload, the difference became visible almost immediately.&lt;/p&gt;

&lt;p&gt;Earlier, after roughly an hour and a half of active work, I had already used about 18.8% of the Premium weekly allowance.&lt;/p&gt;

&lt;p&gt;Now, despite working much less intensively because of this entire issue, I am already at &lt;strong&gt;38% of the weekly limit&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The next reset is Monday, November 23.&lt;/p&gt;

&lt;p&gt;That changes how I work.&lt;/p&gt;

&lt;p&gt;Instead of thinking only about the development task, I now also have to think about whether the next coding run is worth spending part of the remaining weekly pool.&lt;/p&gt;

&lt;p&gt;Avoiding exactly that kind of calculation was one of the reasons I bought Ultra in the first place.&lt;/p&gt;

&lt;h2&gt;
  
  
  This is not a “Cursor is bad” post
&lt;/h2&gt;

&lt;p&gt;I want to make that very clear.&lt;/p&gt;

&lt;p&gt;I like Cursor.&lt;/p&gt;

&lt;p&gt;That is why I bought Ultra and why losing the plan is actually a problem for me.&lt;/p&gt;

&lt;p&gt;I also don’t think The X Subscription is automatically bad.&lt;/p&gt;

&lt;p&gt;For someone actively using Cursor, Grok, Grok Bot, and X, having a single subscription and shared usage pool may be genuinely useful.&lt;/p&gt;

&lt;p&gt;My issue is with the migration experience.&lt;/p&gt;

&lt;p&gt;When an account operation is permanent and can affect a recently purchased subscription, the user needs to understand exactly what will happen before confirming it.&lt;/p&gt;

&lt;p&gt;In my case, I contacted support precisely because I didn’t want to make a mistake.&lt;/p&gt;

&lt;p&gt;Following that support recommendation left me in a worse state than before I asked for help.&lt;/p&gt;

&lt;h2&gt;
  
  
  Billing still has a chance to resolve this properly
&lt;/h2&gt;

&lt;p&gt;My support ticket, &lt;strong&gt;T-K32987&lt;/strong&gt;, has now been escalated to a human billing specialist.&lt;/p&gt;

&lt;p&gt;I’m not asking for anything excessive.&lt;/p&gt;

&lt;p&gt;Any one of these outcomes would resolve the issue for me:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;restore an equivalent Ultra subscription at the price I paid;&lt;/li&gt;
&lt;li&gt;provide enough credit or discount to restore the equivalent plan;&lt;/li&gt;
&lt;li&gt;refund the full amount I originally paid, roughly $100.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That’s it.&lt;/p&gt;

&lt;p&gt;I don’t want free months or some huge compensation.&lt;/p&gt;

&lt;p&gt;I simply don’t want to lose money or working capacity because I followed the instructions given by support.&lt;/p&gt;

&lt;p&gt;If billing resolves it properly, I will update this article. I think it is only fair to document the resolution as clearly as the problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  The bigger lesson for me is about dependency
&lt;/h2&gt;

&lt;p&gt;This incident made me think about something beyond billing.&lt;/p&gt;

&lt;p&gt;Over the last few months, I have been trying to make my AI-development workflow less dependent on any single model or coding agent.&lt;/p&gt;

&lt;p&gt;Until now, I mostly thought about that as a technical problem.&lt;/p&gt;

&lt;p&gt;Maybe Cursor is better for one type of task, Claude Code for another, Grok for research, or Codex for something else.&lt;/p&gt;

&lt;p&gt;But subscription systems, usage limits, account migrations, and pricing changes create another kind of dependency.&lt;/p&gt;

&lt;p&gt;You can build a very good development workflow around one tool and still discover that a billing or account issue can suddenly block a large part of your work.&lt;/p&gt;

&lt;p&gt;That is why I have now started looking more seriously at &lt;strong&gt;Claude Code as an alternative executor&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Not because I suddenly dislike Cursor.&lt;/p&gt;

&lt;p&gt;Because I no longer want one subscription to determine whether I can continue development that day.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I would do differently now
&lt;/h2&gt;

&lt;p&gt;If I could go back to the moment before the merge, I would not click it nearly as casually.&lt;/p&gt;

&lt;p&gt;Especially if you currently have:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a legacy Cursor plan;&lt;/li&gt;
&lt;li&gt;promotional pricing;&lt;/li&gt;
&lt;li&gt;multiple Cursor or Grok accounts;&lt;/li&gt;
&lt;li&gt;an Apple or Google Play subscription;&lt;/li&gt;
&lt;li&gt;an existing Ultra or annual subscription.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I would first verify exactly which account becomes primary, which subscription survives, whether a plan switch is involved, what refund will be issued, and whether the old plan can still be purchased afterward.&lt;/p&gt;

&lt;p&gt;The official documentation now explicitly says that completed unification is permanent.&lt;/p&gt;

&lt;p&gt;That alone is a good reason to treat the button with much more caution than I did.&lt;/p&gt;

&lt;p&gt;My story started with something completely ordinary: I wanted Grok Bot on my phone.&lt;/p&gt;

&lt;p&gt;A few steps later, I had lost the Cursor Ultra plan I bought nine days earlier.&lt;/p&gt;

&lt;p&gt;Maybe billing will fix everything and this will end up being nothing more than an annoying migration bug.&lt;/p&gt;

&lt;p&gt;I hope so.&lt;/p&gt;

&lt;p&gt;But for now, my first experience with the new Cursor + Grok account system has taught me one very practical lesson:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;an AI coding workflow should not depend so heavily on one account, one subscription, or one executor that a billing issue can stop development.&lt;/strong&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  References
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://x.ai/news/x-subscription" rel="noopener noreferrer"&gt;Introducing The X Subscription — xAI&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.x.ai/x-subscription/multiple-cursor-accounts" rel="noopener noreferrer"&gt;Multiple Cursor accounts — xAI Docs&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.x.ai/x-subscription/unify-accounts" rel="noopener noreferrer"&gt;Account unification — xAI Docs&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://forum.cursor.com/" rel="noopener noreferrer"&gt;Cursor community reports about Grok Bot/account migration issues&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>productivity</category>
      <category>software</category>
      <category>tools</category>
    </item>
    <item>
      <title>I Made My Original MAG Ecosystem Public</title>
      <dc:creator>Magshifter</dc:creator>
      <pubDate>Wed, 04 Nov 2026 16:41:59 +0000</pubDate>
      <link>https://dev.to/magshifter/i-made-my-original-mag-ecosystem-public-bm2</link>
      <guid>https://dev.to/magshifter/i-made-my-original-mag-ecosystem-public-bm2</guid>
      <description>&lt;p&gt;A couple of months ago, I started building something to make my AI-assisted development workflow more organized.&lt;/p&gt;

&lt;p&gt;At the time, I wasn't trying to create a large framework. I just wanted to solve problems I kept running into: scattered documentation, lost context, inconsistent AI instructions, and too much manual work between development sessions.&lt;/p&gt;

&lt;p&gt;That's how &lt;strong&gt;MAG Ecosystem&lt;/strong&gt; started.&lt;/p&gt;

&lt;p&gt;Over time, it grew into a collection of tools and rules for managing development workflows.&lt;/p&gt;

&lt;p&gt;Today, I'm making that earlier work available publicly as &lt;strong&gt;MAG-Ecosystem-Legacy&lt;/strong&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  What's inside?
&lt;/h3&gt;

&lt;p&gt;The repository contains real tools and documentation from that stage of development:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Knowledge Index &amp;amp; Locator&lt;/strong&gt; — deterministic indexing and lookup for project documentation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cursor integration&lt;/strong&gt; — rules for controlling how AI assistants access development knowledge.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Model Routing Guard&lt;/strong&gt; — optional hooks for managing model-routing behavior.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Documentation Mirror&lt;/strong&gt; — tools for transferring documentation between local repositories and a separate mirror.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Development governance&lt;/strong&gt; — the original rules, processes, and documentation structure.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;XenForo templates&lt;/strong&gt; — documentation templates used in my earlier projects.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It's written mainly around PowerShell 7 and my original Windows development environment.&lt;/p&gt;

&lt;p&gt;The code is available under the MIT license.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why publish the old version?
&lt;/h3&gt;

&lt;p&gt;Because I think showing how a project evolves is just as interesting as showing the final result.&lt;/p&gt;

&lt;p&gt;MAG Ecosystem wasn't perfect. Some architectural decisions worked, others eventually became limitations.&lt;/p&gt;

&lt;p&gt;But it was real. I used it while developing my own projects, discovered problems, and gradually changed my approach.&lt;/p&gt;

&lt;p&gt;That experience eventually led me to &lt;strong&gt;MAG Development Center (MAGDC)&lt;/strong&gt; — a separate project focused on governance, evidence, and controlled AI-assisted development.&lt;/p&gt;

&lt;p&gt;MAGDC is not a drop-in replacement for the old tools. It's the next step in the idea.&lt;/p&gt;

&lt;h3&gt;
  
  
  Explore the project
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;GitHub — source code and documentation:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/Magshifter/MAG-Ecosystem-Legacy" rel="noopener noreferrer"&gt;https://github.com/Magshifter/MAG-Ecosystem-Legacy&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Official forum page:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://magshifter.com/resources/mag-ecosystem-legacy.17/" rel="noopener noreferrer"&gt;https://magshifter.com/resources/mag-ecosystem-legacy.17/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The repository includes English and Ukrainian manuals. The public source is available now, although a packaged GitHub Release hasn't been published and installation on a separate clean Windows machine hasn't yet been verified.&lt;/p&gt;

&lt;p&gt;Legacy development is closed. I'm keeping it available as a historical reference rather than continuing it as a separate product.&lt;/p&gt;

&lt;p&gt;I'm still actively developing MAGDC, and I plan to share more of that process as it progresses.&lt;/p&gt;

&lt;p&gt;If you're experimenting with AI-assisted software development, I'd be interested to hear how you manage context, documentation, and verification in your own projects.&lt;/p&gt;

&lt;p&gt;Sometimes the most useful part of a project is understanding why its architecture had to change.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;code&gt;#opensource&lt;/code&gt; &lt;code&gt;#ai&lt;/code&gt; &lt;code&gt;#devtools&lt;/code&gt; &lt;code&gt;#github&lt;/code&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>opensource</category>
      <category>productivity</category>
      <category>tools</category>
    </item>
    <item>
      <title>When AI Surprised Me Not by Breaking the Rules, but by How It Used Them</title>
      <dc:creator>Magshifter</dc:creator>
      <pubDate>Tue, 27 Oct 2026 18:42:45 +0000</pubDate>
      <link>https://dev.to/magshifter/when-ai-surprised-me-not-by-breaking-the-rules-but-by-how-it-used-them-243j</link>
      <guid>https://dev.to/magshifter/when-ai-surprised-me-not-by-breaking-the-rules-but-by-how-it-used-them-243j</guid>
      <description>&lt;p&gt;Until recently, &lt;strong&gt;MAG Development Center (MAGDC)&lt;/strong&gt; had mainly been tested through XenForo add-on development.&lt;/p&gt;

&lt;p&gt;I wanted to find out: &lt;strong&gt;How would the system behave with a completely different type of project?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;That's how &lt;strong&gt;MAG Business CRM&lt;/strong&gt; began — an experiment in building an order management system for 3D printing using Google Sheets and Google Apps Script.&lt;/p&gt;

&lt;p&gt;And recently, something genuinely surprised me.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happened?
&lt;/h2&gt;

&lt;p&gt;I gave the AI executor a specific task: turn the functionality of a Google Sheets-based system into a web interface with clearly defined technical capabilities.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;I didn't say a single word about design.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;But when I saw the finished interface, I immediately recognized design patterns we'd been developing in MAGDC.&lt;/p&gt;

&lt;p&gt;Why is that interesting?&lt;/p&gt;

&lt;p&gt;MAGDC includes an evolving system of independent design libraries, reusable components, usage rules, and validation mechanisms.&lt;/p&gt;

&lt;p&gt;And suddenly, in a project completely unrelated to XenForo, I saw a familiar design approach appear without explicitly requesting it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Coincidence or architecture at work?
&lt;/h2&gt;

&lt;p&gt;That's what I still need to investigate.&lt;/p&gt;

&lt;p&gt;Did the executor actually use a MAGDC design library? Or did it simply reproduce a similar visual style?&lt;/p&gt;

&lt;p&gt;And more importantly, did it stay within its authority?&lt;/p&gt;

&lt;p&gt;Because &lt;strong&gt;reusing an approved solution and independently changing a product's design standards are two very different things.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;But the result made me think.&lt;/p&gt;

&lt;p&gt;Maybe we're gradually approaching what I originally wanted MAGDC to achieve:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;I define WHAT needs to be done, while AI figures out HOW — using accumulated knowledge without crossing established boundaries.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Now I want to find out whether this really was the result of MAGDC's mechanisms.&lt;/p&gt;

&lt;p&gt;If it was, that would mean far more to me than simply getting a good-looking interface.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Because the real value of a system of rules isn't how many restrictions it imposes. It's how much more it enables us to accomplish without having to supervise every step.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;And perhaps this was the first time I'd seen that happen in practice.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/Magshifter/MAG-Development-Center" rel="noopener noreferrer"&gt;MAG Development Center on GitHub&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>design</category>
      <category>softwaredevelopment</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Can I Turn MAGDC Into Something Bigger Than a Coding System?</title>
      <dc:creator>Magshifter</dc:creator>
      <pubDate>Tue, 27 Oct 2026 11:28:13 +0000</pubDate>
      <link>https://dev.to/magshifter/can-i-turn-magdc-into-something-bigger-than-a-coding-system-1e25</link>
      <guid>https://dev.to/magshifter/can-i-turn-magdc-into-something-bigger-than-a-coding-system-1e25</guid>
      <description>&lt;p&gt;I've been asking myself an interesting question lately.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Am I building a system for developing software, or could it eventually become a system for developing almost anything?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A few months ago, I started building &lt;strong&gt;MAGDC (MAG Development Center)&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The idea was to solve problems I kept running into while developing software with AI: forgotten decisions, unexpected changes, broken functionality, and agents doing more than I actually asked.&lt;/p&gt;

&lt;p&gt;MAGDC doesn't write the code itself. It helps me organize requirements, decisions, architecture, tasks, and verification while AI tools such as Cursor handle implementation.&lt;/p&gt;

&lt;p&gt;My main testing ground has been &lt;strong&gt;XenForo add-on development&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;But I wanted to see whether the same approach would work somewhere else.&lt;/p&gt;

&lt;h2&gt;
  
  
  My first experiment beyond XenForo
&lt;/h2&gt;

&lt;p&gt;I'm currently finishing &lt;strong&gt;MAG Business CRM&lt;/strong&gt;, built with Google Sheets and Google Apps Script for managing 3D printing orders.&lt;/p&gt;

&lt;p&gt;It handles things like customers, materials, pricing, production orders, payments, and financial calculations.&lt;/p&gt;

&lt;p&gt;What makes this interesting to me isn't simply that AI helped build a CRM.&lt;/p&gt;

&lt;p&gt;It's how we developed it.&lt;/p&gt;

&lt;p&gt;I defined the business requirements, made the important decisions, and used MAGDC to organize the work into manageable steps. Cursor implemented the changes and ran technical checks.&lt;/p&gt;

&lt;p&gt;And we learned something important along the way.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Passing tests doesn't necessarily mean the product is good to use.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For example, an order management screen passed technical checks, but when I tried using it, the selected order's details appeared below a long list. With just twenty orders, that was already inconvenient.&lt;/p&gt;

&lt;p&gt;So we changed the interface based on actual usage.&lt;/p&gt;

&lt;p&gt;Other seemingly small requests, such as giving orders readable numbers or preserving financial history, turned out to require much more careful architectural decisions.&lt;/p&gt;

&lt;p&gt;The CRM has substantial implemented and tested functionality, although its final end-to-end validation and practical acceptance are still ahead.&lt;/p&gt;

&lt;p&gt;It's not proof that MAGDC works everywhere. But it is useful experience outside its original XenForo environment.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's next?
&lt;/h2&gt;

&lt;p&gt;I've also worked on a Windows utility connecting ChatGPT and Cursor.&lt;/p&gt;

&lt;p&gt;Now I'm considering something very different: &lt;strong&gt;developing a civilian racing drone&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;I want to explore whether MAGDC could help organize not just programming, but also CAD models, engineering requirements, prototypes, documentation, and physical testing.&lt;/p&gt;

&lt;p&gt;The MAGDC repository already has a planned embedded/FPV domain, but that doesn't mean the engineering workflow has been proven.&lt;/p&gt;

&lt;p&gt;And that's exactly what I want to discover.&lt;/p&gt;

&lt;p&gt;Maybe MAGDC's approach will transfer well.&lt;/p&gt;

&lt;p&gt;Maybe I'll find that some of its rules only make sense for software.&lt;/p&gt;

&lt;p&gt;Either result would teach me something.&lt;/p&gt;

&lt;p&gt;I'm increasingly interested in building a system where one person can coordinate complex projects with AI assistance — while keeping the important decisions under human control.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can an AI development workflow designed for software eventually help create physical products too?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I don't know yet. But I intend to test it.&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>productivity</category>
      <category>softwaredevelopment</category>
      <category>systemdesign</category>
    </item>
    <item>
      <title>Cursor Hit Its Usage Limit. Grok Picked Up Where It Left Off.</title>
      <dc:creator>Magshifter</dc:creator>
      <pubDate>Sun, 25 Oct 2026 21:16:29 +0000</pubDate>
      <link>https://dev.to/magshifter/cursor-hit-its-usage-limit-grok-picked-up-where-it-left-off-448g</link>
      <guid>https://dev.to/magshifter/cursor-hit-its-usage-limit-grok-picked-up-where-it-left-off-448g</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fyj70b7f09c66m0vois04.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fyj70b7f09c66m0vois04.png" alt=" " width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A few days ago, I ran into a familiar problem: I had more development work to do, but I'd reached my Cursor usage limit.&lt;/p&gt;

&lt;p&gt;Normally, that would mean taking a break or waiting for the limit to reset.&lt;/p&gt;

&lt;p&gt;This time, I decided to try something different.&lt;/p&gt;

&lt;p&gt;I had Grok Bot available. I'd mostly used it for research, code reviews, and technical audits, but I knew it could work with code too.&lt;/p&gt;

&lt;p&gt;So I gave it my next development task.&lt;/p&gt;

&lt;p&gt;And surprisingly, it just got to work.&lt;/p&gt;

&lt;p&gt;Grok connected to my local development environment, worked directly with the Git repository, ran the required checks, and committed and pushed the changes.&lt;/p&gt;

&lt;p&gt;It wasn't controlling Cursor or forwarding tasks to another coding agent. It was doing the work itself.&lt;/p&gt;

&lt;h2&gt;
  
  
  But there was a catch
&lt;/h2&gt;

&lt;p&gt;I'd already experimented with Grok as a coding agent before.&lt;/p&gt;

&lt;p&gt;Its technical work was good, but it had a habit of taking shortcuts. Sometimes it would make decisions I hadn't approved or skip parts of my development workflow to reach the result faster.&lt;/p&gt;

&lt;p&gt;The code might be fine, but the process wasn't.&lt;/p&gt;

&lt;p&gt;And that's something I've been trying to solve with &lt;strong&gt;MAGDC (MAG Development Center)&lt;/strong&gt;, a system I'm building to manage AI-assisted software development.&lt;/p&gt;

&lt;p&gt;Before this experiment, I'd updated the MAGDC skills used by Grok. These skills help the agent find the current project rules, understand its task boundaries, and know when it needs to stop and ask for a decision.&lt;/p&gt;

&lt;p&gt;This time, I noticed a difference.&lt;/p&gt;

&lt;p&gt;Grok stayed within the assigned scope, followed the required checks, and stopped when a task needed my approval instead of improvising its own solution.&lt;/p&gt;

&lt;p&gt;It completed several development tasks this way.&lt;/p&gt;

&lt;p&gt;Of course, a few successful runs don't prove that this approach will always work. I still need to test it across different types of tasks.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I found interesting
&lt;/h2&gt;

&lt;p&gt;The biggest surprise wasn't that Grok could write code.&lt;/p&gt;

&lt;p&gt;It was that I could switch AI coding tools without having to rebuild my entire development process around a different assistant.&lt;/p&gt;

&lt;p&gt;The project requirements, decisions, and rules remained in the repository. The next task was already defined.&lt;/p&gt;

&lt;p&gt;I only changed the executor.&lt;/p&gt;

&lt;p&gt;Cursor is still my main development tool, and I'm not planning to replace it. But this experience made me think differently about how I use AI agents.&lt;/p&gt;

&lt;p&gt;Maybe the goal shouldn't be finding one perfect AI coding assistant.&lt;/p&gt;

&lt;p&gt;Maybe it's building a workflow where different agents can work on the same project without losing the decisions and rules that matter.&lt;/p&gt;

&lt;p&gt;That's what I'm exploring with MAGDC.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;I'm curious: have you ever switched AI coding agents in the middle of a project? Did the new agent follow your existing workflow, or did you have to start explaining everything again?&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>productivity</category>
      <category>tools</category>
    </item>
    <item>
      <title>Two Months Ago I Was Flying Agricultural Drones. Now I'm Building Software with AI.</title>
      <dc:creator>Magshifter</dc:creator>
      <pubDate>Sun, 25 Oct 2026 19:38:49 +0000</pubDate>
      <link>https://dev.to/magshifter/two-months-ago-i-was-flying-agricultural-drones-now-im-building-software-with-ai-46g5</link>
      <guid>https://dev.to/magshifter/two-months-ago-i-was-flying-agricultural-drones-now-im-building-software-with-ai-46g5</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuw4pc8emwrex05v8gv0m.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuw4pc8emwrex05v8gv0m.png" alt=" " width="339" height="460"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  Hi! I'm Yevhen, 42, from Sumy, Ukraine.
&lt;/h1&gt;

&lt;p&gt;I'm a stop-motion animator, and until recently, my programming knowledge was limited to some CSS. I'd heard of HTML, but that was about it.&lt;/p&gt;

&lt;p&gt;Almost two months ago, I was working as an agricultural drone pilot, spending my days out in the fields. That's when I started experimenting with AI coding tools.&lt;/p&gt;

&lt;p&gt;I had plenty of ideas but no idea how to turn them into working software. AI changed that.&lt;/p&gt;

&lt;p&gt;At first, it felt almost too easy. I described what I wanted, and AI wrote the code.&lt;/p&gt;

&lt;p&gt;But as my projects grew, things got messy.&lt;/p&gt;

&lt;p&gt;AI would fix one problem and create another, forget previous decisions, or confidently report that something was finished when it wasn't.&lt;/p&gt;

&lt;p&gt;And without much programming experience, I couldn't always spot those mistakes.&lt;/p&gt;

&lt;p&gt;So I started building &lt;strong&gt;MAGDC (MAG Development Center)&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;It's not another AI coding assistant. It's a system I'm developing to help manage AI-driven software projects: requirements, decisions, tasks, and verification of completed work.&lt;/p&gt;

&lt;p&gt;I'm already using it while developing real projects, and it's still evolving.&lt;/p&gt;

&lt;p&gt;It's funny how things turn out. Two months ago, I was flying agricultural drones. Now I'm learning about software architecture, Git, and development workflows.&lt;/p&gt;

&lt;p&gt;I decided to share this journey here — what works, what doesn't, and what I learn along the way.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;For those building software with AI agents: what's your biggest challenge?&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>beginners</category>
      <category>career</category>
      <category>learning</category>
    </item>
  </channel>
</rss>
