<?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: Akshay Kumar</title>
    <description>The latest articles on DEV Community by Akshay Kumar (@akshay0611).</description>
    <link>https://dev.to/akshay0611</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%2F3800843%2Ffda642be-938c-455f-95c7-e4dde46eef9d.jpg</url>
      <title>DEV Community: Akshay Kumar</title>
      <link>https://dev.to/akshay0611</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/akshay0611"/>
    <language>en</language>
    <item>
      <title>Building a Production LMS: Architecture, Payments, and Content Protection</title>
      <dc:creator>Akshay Kumar</dc:creator>
      <pubDate>Tue, 27 Oct 2026 15:40:41 +0000</pubDate>
      <link>https://dev.to/akshay0611/building-a-production-lms-architecture-payments-and-content-protection-50h7</link>
      <guid>https://dev.to/akshay0611/building-a-production-lms-architecture-payments-and-content-protection-50h7</guid>
      <description>&lt;h1&gt;
  
  
  Building a Production LMS: Architecture, Payments, and Content Protection
&lt;/h1&gt;

&lt;p&gt;A learning management system looks straightforward from the outside. Students browse courses, make payments, watch lessons, and attend live classes.&lt;/p&gt;

&lt;p&gt;But building one for a real education business quickly introduces problems that aren't visible in the UI.&lt;/p&gt;

&lt;p&gt;What happens when a payment succeeds but the enrolment isn't activated? How do you prevent a purchased course from becoming a shared login across multiple devices? How should a mobile app and an admin console enforce the same business rules? And what happens when payment notifications arrive more than once or a request fails halfway through a workflow?&lt;/p&gt;

&lt;p&gt;I worked on these challenges while building the MBT Institute LMS, a production learning platform with a Flutter Android app, a NestJS backend, and a Next.js administration console.&lt;/p&gt;

&lt;p&gt;In this article, I want to walk through the architecture, explain some of the engineering decisions behind it, and share lessons that may help if you're building an LMS or another platform where payments control access to digital content.&lt;/p&gt;

&lt;p&gt;The interesting part wasn't simply choosing a tech stack. It was making sure authentication, payments, enrolments, device access, and content delivery behaved consistently as parts of one system.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. The architecture: three applications, one backend
&lt;/h2&gt;

&lt;p&gt;I chose to separate the platform into three independently deployable applications:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Flutter:&lt;/strong&gt; the Android application for learners.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;NestJS:&lt;/strong&gt; the backend API responsible for business logic and integrations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Next.js:&lt;/strong&gt; the administration console for operational workflows.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Supabase PostgreSQL provides the relational data layer, with supporting services for authentication, payments, media delivery, notifications, live classes, and background processing.&lt;/p&gt;

&lt;p&gt;Here's a simplified view of how the components fit together:&lt;/p&gt;

&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%2Fbfw9hnog2y3ztjq8u6sm.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%2Fbfw9hnog2y3ztjq8u6sm.png" alt=" " width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This is a logical architecture rather than an exhaustive deployment diagram. It illustrates the important boundary: both client applications use the same backend rules instead of implementing separate versions of payment validation and course-access logic.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why not put everything in the frontend?
&lt;/h3&gt;

&lt;p&gt;Because a frontend is not a security boundary.&lt;/p&gt;

&lt;p&gt;A user can modify a client, replay requests, or call an API directly. Hiding a button or checking a condition in Flutter doesn't prevent someone from bypassing that condition.&lt;/p&gt;

&lt;p&gt;The backend must remain authoritative for payment verification, enrolment eligibility, device authorization, and access to protected resources.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Designing the data model around business rules
&lt;/h2&gt;

&lt;p&gt;One of the most important decisions is how to represent the relationships between learners, purchases, and course access.&lt;/p&gt;

&lt;p&gt;At a conceptual level, I'd start with entities such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;users&lt;/code&gt; and &lt;code&gt;profiles&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;courses&lt;/code&gt;, &lt;code&gt;sections&lt;/code&gt;, and &lt;code&gt;lessons&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;orders&lt;/code&gt; and &lt;code&gt;order_items&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;&lt;code&gt;payments&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;enrollments&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;devices&lt;/code&gt; and &lt;code&gt;device_transfer_requests&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;&lt;code&gt;invoices&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;live_sessions&lt;/code&gt; and &lt;code&gt;recordings&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An order represents what a learner intends to purchase. A payment records the provider transaction. An enrolment represents the learner's entitlement to a course.&lt;/p&gt;

&lt;p&gt;These concepts are related, but they aren't interchangeable.&lt;/p&gt;

&lt;p&gt;If a student says, "I paid, but I can't access the course," you need to investigate the order, payment status, enrolment, and device association independently.&lt;/p&gt;

&lt;p&gt;That becomes difficult if course access is activated simply because the frontend redirects to a success page.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;My takeaway:&lt;/strong&gt; model the business entities and their relationships before building the checkout UI.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Payment processing: success isn't just a redirect
&lt;/h2&gt;

&lt;p&gt;Consider a typical checkout flow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The learner selects a course and initiates checkout.&lt;/li&gt;
&lt;li&gt;The backend validates the course, price, applicable commercial rules, and coupon.&lt;/li&gt;
&lt;li&gt;The backend creates an order associated with the relevant payment workflow.&lt;/li&gt;
&lt;li&gt;The learner completes checkout through Razorpay.&lt;/li&gt;
&lt;li&gt;The backend verifies the payment using trusted provider information.&lt;/li&gt;
&lt;li&gt;The verified payment is recorded, and the appropriate enrolment is activated.&lt;/li&gt;
&lt;li&gt;The corresponding invoice becomes available through the billing workflow.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The frontend redirect must never be the authority for activating an enrolment.&lt;/p&gt;

&lt;p&gt;A request can time out. A learner can close the app. A payment notification can arrive more than once. A server can fail after updating one record but before completing another operation.&lt;/p&gt;

&lt;p&gt;This is where &lt;strong&gt;idempotency&lt;/strong&gt; becomes essential.&lt;/p&gt;

&lt;p&gt;Processing the same verified payment event repeatedly should not create duplicate enrolments or invoices. Database constraints and transactions should protect critical relationships, while asynchronous work needs a reliable handoff and retry strategy.&lt;/p&gt;

&lt;p&gt;For example, a payment event can be received twice because of a provider retry. Your system should recognize that it has already processed the relevant transaction rather than blindly repeating every side effect.&lt;/p&gt;

&lt;p&gt;The implementation details depend on the provider's event semantics and your transaction boundaries, but the principle is consistent: payment verification and entitlement activation must form an explicit, recoverable workflow.&lt;/p&gt;

&lt;h3&gt;
  
  
  Questions worth answering before shipping checkout
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;What happens if payment succeeds but the client times out?&lt;/li&gt;
&lt;li&gt;What happens if the same webhook is delivered twice?&lt;/li&gt;
&lt;li&gt;How do cancellations and refunds affect enrolment?&lt;/li&gt;
&lt;li&gt;How can an administrator reconcile a completed payment with a missing invoice?&lt;/li&gt;
&lt;li&gt;Can the system safely retry a partially completed workflow?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These aren't edge cases to consider after launch. They're part of the payment lifecycle.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Content protection: authentication is not entitlement
&lt;/h2&gt;

&lt;p&gt;Content protection was another central requirement.&lt;/p&gt;

&lt;p&gt;A successful login tells us that a user has authenticated. It does not automatically mean that the user is entitled to every course or that the current device is authorized to access a particular enrolment.&lt;/p&gt;

&lt;p&gt;I approached this as a layered problem.&lt;/p&gt;

&lt;h3&gt;
  
  
  Device-bound access
&lt;/h3&gt;

&lt;p&gt;Each enrolment is associated with one active device. A device identifier is maintained using secure storage, and the backend validates the association when access is requested.&lt;/p&gt;

&lt;p&gt;Signing in on a second phone does not automatically grant that device access to the same enrolment.&lt;/p&gt;

&lt;p&gt;The critical part is server-side enforcement. A device check that exists only inside the mobile app can potentially be bypassed by modifying the client or calling the API directly.&lt;/p&gt;

&lt;p&gt;A device identifier also isn't cryptographic proof of identity. The backend still needs to validate the authenticated session, course entitlement, and device association rather than blindly trusting an identifier supplied by the client.&lt;/p&gt;

&lt;h3&gt;
  
  
  Controlled device transfers
&lt;/h3&gt;

&lt;p&gt;Students replace phones and lose devices. A strict device lock without a recovery process would turn a reasonable security control into a support problem.&lt;/p&gt;

&lt;p&gt;The platform includes an administrator-reviewed device-transfer workflow so legitimate device changes can be handled without treating every new device as automatically authorized.&lt;/p&gt;

&lt;p&gt;This is a useful general principle:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Every restrictive security control needs a legitimate recovery path.&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Protected media delivery
&lt;/h3&gt;

&lt;p&gt;Protected media and resources should be delivered through authorized, short-lived URLs rather than intentionally exposed public links. Playback surfaces can also use platform-supported screenshot restrictions where appropriate.&lt;/p&gt;

&lt;p&gt;These controls reduce casual copying and limit the usefulness of leaked links, but they cannot make piracy impossible. Someone can record a screen using another device, and sufficiently determined attackers may find other ways to reproduce content.&lt;/p&gt;

&lt;p&gt;The goal is layered protection: authenticate the learner, verify the entitlement, validate the device, and restrict access to the media itself.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Where PostgreSQL RLS fits
&lt;/h2&gt;

&lt;p&gt;Supabase Row Level Security and backend authorization solve related but different problems.&lt;/p&gt;

&lt;p&gt;RLS can restrict which database rows a user or role can access. Application-level authorization can enforce domain-specific rules, such as whether a particular enrolment grants access to a particular lesson.&lt;/p&gt;

&lt;p&gt;Both layers need deliberate design.&lt;/p&gt;

&lt;p&gt;For a similar project, I'd review every table exposed to client access, enable appropriate RLS policies, and ensure privileged server credentials never reach the mobile application or browser.&lt;/p&gt;

&lt;p&gt;Privileged database functions and backend operations should also be narrowly scoped and validate their inputs.&lt;/p&gt;

&lt;p&gt;A few things I'd pay particular attention to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Don't assume hiding a UI element provides authorization.&lt;/li&gt;
&lt;li&gt;Don't expose service-role credentials in a client application.&lt;/li&gt;
&lt;li&gt;Keep database policies consistent with the intended access model.&lt;/li&gt;
&lt;li&gt;Test unauthorized reads and writes, not only successful user journeys.&lt;/li&gt;
&lt;li&gt;Review privileged functions for overly broad permissions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;RLS is powerful, but it doesn't replace application security reviews or a clear authorization model.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Separating commercial rules
&lt;/h2&gt;

&lt;p&gt;The platform supports hardware and software course categories with different commercial rules. Their payment configurations, coupon applicability, and reporting requirements need to remain consistent with those distinctions.&lt;/p&gt;

&lt;p&gt;Coupons are validated by the backend before discounts are applied, and purchases maintain transaction-level payment and enrolment records.&lt;/p&gt;

&lt;p&gt;The important design point is that pricing and eligibility must not be trusted to the client. A modified request should not be able to change the price, apply an ineligible coupon, or claim access to a course without a verified transaction or other valid entitlement.&lt;/p&gt;

&lt;p&gt;I'd define these rules before building the checkout interface. Retrofitting them later is much harder once multiple clients, reports, and administrative workflows depend on the same data.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Live classes, recordings, and background jobs
&lt;/h2&gt;

&lt;p&gt;The platform also integrates Zoom for live-class scheduling and supports publishing recordings back into the course experience.&lt;/p&gt;

&lt;p&gt;Redis and BullMQ provide a foundation for asynchronous processing where it makes sense. Notification delivery and other retryable work can be separated from the user-facing request that initiated it.&lt;/p&gt;

&lt;p&gt;Queues can improve responsiveness, but they introduce operational responsibilities.&lt;/p&gt;

&lt;p&gt;Jobs need appropriate retry policies. Failures need visibility. Operations with side effects need to be safe to execute more than once.&lt;/p&gt;

&lt;p&gt;A queue alone doesn't make a workflow reliable. Reliability comes from durable state, safe retries, observability, and a clear recovery strategy.&lt;/p&gt;

&lt;p&gt;I'd avoid introducing background processing for everything. Start with the workflows that benefit from asynchronous execution, then make their failure and retry behavior explicit.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Production is where the architecture gets tested
&lt;/h2&gt;

&lt;p&gt;The Android app launched on Google Play in October 2026. After launch, the work shifted from getting the product shipped to understanding how it behaved under real usage.&lt;/p&gt;

&lt;p&gt;Production monitoring matters because several different signals tell different stories:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Downloads&lt;/strong&gt; indicate distribution, not necessarily active learners.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Payment records&lt;/strong&gt; show transactions, not automatically recognized revenue or profit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;API request counts&lt;/strong&gt; show traffic, not user engagement.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Response errors and latency&lt;/strong&gt; help reveal reliability and performance problems.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;During the production review, we examined Supabase API Gateway traffic and response errors alongside backend request metrics. Those numbers came from different systems and reporting windows, so they needed to be interpreted separately rather than combined into a single headline metric.&lt;/p&gt;

&lt;p&gt;The operational lesson is that launch is only one milestone. Monitoring, capacity planning, resource alerts, backups, restore testing, and incident response are all part of running a production system.&lt;/p&gt;

&lt;p&gt;If I were preparing a similar platform for launch, I'd want to know:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Can I identify failed payment-to-enrolment workflows?&lt;/li&gt;
&lt;li&gt;Can I trace a learner's access decision across the relevant records?&lt;/li&gt;
&lt;li&gt;Do I have alerts for elevated error rates and latency?&lt;/li&gt;
&lt;li&gt;Have I tested restoring a backup, not just creating one?&lt;/li&gt;
&lt;li&gt;Can an administrator resolve common operational issues without direct database edits?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;These capabilities become increasingly important as the platform grows.&lt;/p&gt;

&lt;h2&gt;
  
  
  9. If I were building an LMS from scratch today
&lt;/h2&gt;

&lt;p&gt;I'd approach the work in this order.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Define the domain model.&lt;/strong&gt; Establish the relationships between users, courses, orders, payments, enrolments, and devices.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Implement authentication and authorization.&lt;/strong&gt; Define learner and administrator roles, course-entitlement checks, and RLS policies.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Build the payment lifecycle.&lt;/strong&gt; Add server-side price validation, provider verification, idempotent processing, enrolment activation, and reconciliation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Protect content access.&lt;/strong&gt; Implement device binding, transfer workflows, and authorized media delivery.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Build the administration console.&lt;/strong&gt; Give staff the tools to manage courses, billing, device transfers, and support.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6. Add integrations.&lt;/strong&gt; Introduce live classes, notifications, and background jobs where they solve a concrete problem.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;7. Prepare for production.&lt;/strong&gt; Add logging, metrics, alerts, backups, restore tests, and load testing.&lt;/p&gt;

&lt;p&gt;You don't need every integration on day one. A smaller system with correct payment and access semantics is a better foundation than a feature-rich application with inconsistent business rules.&lt;/p&gt;

&lt;h2&gt;
  
  
  10. What I'd take into the next project
&lt;/h2&gt;

&lt;p&gt;A few lessons stood out.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Security belongs in the data model.&lt;/strong&gt; Device associations, enrolments, and transfer workflows are closely connected, so they should be designed together.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Important rules need a clear authority.&lt;/strong&gt; The mobile app and admin console shouldn't independently implement payment validation or course entitlement.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Operational workflows are part of the product.&lt;/strong&gt; Payment reconciliation, device recovery, and support tools determine whether a platform is manageable in production.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Observability should come before a traffic spike.&lt;/strong&gt; Metrics and alerts are most useful when you understand them before an incident.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Security has to account for legitimate users.&lt;/strong&gt; A restrictive system without a practical recovery path creates unnecessary friction for the people it's supposed to protect.&lt;/p&gt;

&lt;p&gt;These lessons apply beyond education technology. They're relevant to subscription products, digital content platforms, training applications, and any system where a transaction controls access to a protected resource.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final thoughts
&lt;/h2&gt;

&lt;p&gt;The most meaningful engineering work often happens behind the screens people see.&lt;/p&gt;

&lt;p&gt;A course page is only one part of the product. Behind it are questions about identity, payment verification, enrolment state, device access, media delivery, retries, and operational recovery.&lt;/p&gt;

&lt;p&gt;Building the MBT Institute LMS reinforced something I believe applies to most production systems: the difficult part isn't making individual components work. It's defining the boundaries between them and ensuring those boundaries remain correct when requests fail, users change devices, or external services behave unexpectedly.&lt;/p&gt;

&lt;p&gt;I'm interested in how other developers approach these problems, particularly idempotent payment processing, device-bound access, and protecting paid digital content.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If you've built something similar, what was the hardest production problem you had to solve?&lt;/strong&gt;&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Explore the case study:&lt;/strong&gt; &lt;a href="https://connectwithakshay.netlify.app/case-studies/mbt-learning-lms-piracy-protection" rel="noopener noreferrer"&gt;Building a Piracy-Resistant LMS — MBT Institute&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Try the app:&lt;/strong&gt; &lt;a href="https://play.google.com/store/apps/details?id=com.tensorik.mbt_lms" rel="noopener noreferrer"&gt;MBT Institute LMS on Google Play&lt;/a&gt;&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>webdev</category>
      <category>typescript</category>
      <category>edtech</category>
    </item>
    <item>
      <title>How I Ranked #2 Out of 25,000+ GSSoC 2025 Contributors: My Open Source Journey</title>
      <dc:creator>Akshay Kumar</dc:creator>
      <pubDate>Sun, 12 Apr 2026 14:46:10 +0000</pubDate>
      <link>https://dev.to/akshay0611/how-i-ranked-2-out-of-3400-gssoc-2025-contributors-my-open-source-journey-18am</link>
      <guid>https://dev.to/akshay0611/how-i-ranked-2-out-of-3400-gssoc-2025-contributors-my-open-source-journey-18am</guid>
      <description>&lt;p&gt;The global developer population exploded to over 180 million in 2025, with India projected to become the world's largest developer hub by 2028. In this landscape, standing out requires more than just knowing how to code — it requires a proven track record of collaboration.&lt;/p&gt;

&lt;p&gt;GirlScript Summer of Code (GSSoC) has become a premier proving ground for students and early-career developers. With GSSoC 2026 just around the corner, here's exactly how I ranked #2 out of 25,000+ contributors in the 2025 edition — and what you can learn from it before you apply.&lt;/p&gt;

&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.amazonaws.com%2Fuploads%2Farticles%2F9yeit0ak0k71l1yoqe56.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.amazonaws.com%2Fuploads%2Farticles%2F9yeit0ak0k71l1yoqe56.png" alt="GSSoC Leaderboard" width="800" height="1531"&gt;&lt;/a&gt;&lt;br&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.amazonaws.com%2Fuploads%2Farticles%2Fc9bxr4p97ikf7yvm06oh.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.amazonaws.com%2Fuploads%2Farticles%2Fc9bxr4p97ikf7yvm06oh.png" alt="GitHub Contribution Graph" width="800" height="364"&gt;&lt;/a&gt;&lt;/p&gt;

&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.amazonaws.com%2Fuploads%2Farticles%2Fbo3ny0zqpjf5gi1b4bvl.webp" 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.amazonaws.com%2Fuploads%2Farticles%2Fbo3ny0zqpjf5gi1b4bvl.webp" alt="My GitHub contribution graph showing 2,361 contributions during GSSoC 2025" width="800" height="211"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;2,361 contributions — the green streak from July to October tells the whole story.&lt;/em&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  🔑 Key Takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Consistency is King:&lt;/strong&gt; My rank was built on 120+ days of daily contributions, not occasional bursts&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Quality Over Quantity:&lt;/strong&gt; High-quality PRs and clear communication were the real drivers of my success&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Go Deep, Not Wide:&lt;/strong&gt; Contributing seriously to two projects beat spreading thin across many&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  What is GSSoC?
&lt;/h2&gt;

&lt;p&gt;GirlScript Summer of Code (GSSoC) is a four-month open-source program that connects student contributors with real-world projects under active mentorship. The 2025 edition had &lt;strong&gt;25,000+ global contributors&lt;/strong&gt; competing on a points-based leaderboard.&lt;/p&gt;

&lt;p&gt;The program is beginner-friendly — but the leaderboard is not. To rank, you need strategy, not just effort.&lt;/p&gt;




&lt;h2&gt;
  
  
  How Did I Reach 2,014 Points?
&lt;/h2&gt;

&lt;p&gt;I focused on two main projects rather than jumping across many repositories:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. &lt;a href="https://talkheal.app/" rel="noopener noreferrer"&gt;TalkHeal&lt;/a&gt;&lt;/strong&gt;&lt;br&gt;
An empathetic mental health support assistant built with Python and Streamlit. I contributed to backend logic, feature improvements, and documentation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. &lt;a href="https://build-on-coffee.vercel.app/" rel="noopener noreferrer"&gt;BuildOnCoffee&lt;/a&gt;&lt;/strong&gt;&lt;br&gt;
An open-source platform for discovering developer tools and CS learning resources, built with React. I focused on frontend component optimization and UI fixes.&lt;/p&gt;

&lt;p&gt;Going deep into two codebases let me build genuine rapport with maintainers and understand the architecture well enough to propose my own feature enhancements — something that earned far more trust (and points) than surface-level fixes.&lt;/p&gt;




&lt;h2&gt;
  
  
  My Git and PR Strategy
&lt;/h2&gt;

&lt;p&gt;Every PR I submitted followed this rule:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Explain &lt;strong&gt;why&lt;/strong&gt; the change was made, not just &lt;strong&gt;what&lt;/strong&gt; changed.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This single habit made my PRs faster to review and merge. Maintainers are busy — if you reduce their mental load, they will prioritize your work.&lt;/p&gt;

&lt;p&gt;My PR checklist for every submission:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Clear title describing the change&lt;/li&gt;
&lt;li&gt;A "Why" section in the description&lt;/li&gt;
&lt;li&gt;Screenshots for any UI changes&lt;/li&gt;
&lt;li&gt;No merge conflicts (rebase before pushing)&lt;/li&gt;
&lt;li&gt;Linked to the relevant issue&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This level of discipline across both Python and React repositories helped me build a reputation as a reliable contributor within the first few weeks.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Consistency Challenge
&lt;/h2&gt;

&lt;p&gt;Staying active for &lt;strong&gt;120 consecutive days&lt;/strong&gt; is what separates top rankers from everyone else. Most contributors burn bright for the first two weeks and then fade.&lt;/p&gt;

&lt;p&gt;My approach was simple: treat GSSoC like a daily appointment.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Mornings:&lt;/strong&gt; Research open issues, plan the day's work&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Evenings:&lt;/strong&gt; Implement, commit, and push&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;On low-energy days, I didn't force complex code. I wrote documentation, reviewed other contributors' PRs, or explored the codebase. The goal was to never let a day go by without adding some value.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;The lesson I learned:&lt;/strong&gt; Some of the most impactful contributions aren't hundreds of lines of code. Fixing a critical bug or improving onboarding docs for new contributors can earn just as much respect — sometimes more.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  What I Actually Gained
&lt;/h2&gt;

&lt;p&gt;The #2 rank is a nice headline, but the real outcome was:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Stronger Git fundamentals&lt;/strong&gt; — rebasing, conflict resolution, branch management&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cross-stack experience&lt;/strong&gt; — Python/Streamlit backend + React frontend&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Code review skills&lt;/strong&gt; — learning to give and receive feedback professionally&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Community trust&lt;/strong&gt; — going from reading code to having my reviews sought out by mentors&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;How many points do I need for GSSoC Top 10?&lt;/strong&gt;&lt;br&gt;
The #2 spot required 2,014 points in 2025. Focus on quality contributions consistently — the rank will follow.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is GSSoC good for absolute beginners?&lt;/strong&gt;&lt;br&gt;
Yes. Many tasks involve documentation, UI fixes, and accessibility improvements — perfect for learning Git workflows before touching complex logic.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Which projects are beginner-friendly?&lt;/strong&gt;&lt;br&gt;
Look for repos with active maintainers who respond within 24–48 hours. &lt;strong&gt;BuildOnCoffee&lt;/strong&gt; and &lt;strong&gt;TalkHeal&lt;/strong&gt; both had excellent mentorship during 2025.&lt;/p&gt;




&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;Don't open the leaderboard on day one. Open an issue instead.&lt;/p&gt;

&lt;p&gt;The ranking is just a byproduct of four months of showing up daily, writing clean code, and treating every PR like it matters — because it does.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Let's connect — I'd love to hear about your open-source journey too.&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;💼 &lt;a href="https://www.linkedin.com/in/akshaykumar0611" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;🐙 &lt;a href="https://github.com/akshay0611" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>gssoc</category>
      <category>opensource</category>
      <category>github</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Build Beautiful App UIs Without Being a Designer — Google Stitch + Antigravity</title>
      <dc:creator>Akshay Kumar</dc:creator>
      <pubDate>Fri, 20 Mar 2026 03:56:30 +0000</pubDate>
      <link>https://dev.to/akshay0611/build-beautiful-app-uis-without-being-a-designer-google-stitch-antigravity-332i</link>
      <guid>https://dev.to/akshay0611/build-beautiful-app-uis-without-being-a-designer-google-stitch-antigravity-332i</guid>
      <description>&lt;p&gt;If you've ever built an app and thought &lt;em&gt;"the logic works great, but it looks terrible"&lt;/em&gt; — this one's for you.&lt;/p&gt;

&lt;p&gt;Most developers, especially students, are strong on the backend and weak on UI. Getting the functionality right is satisfying. Getting it to &lt;em&gt;look&lt;/em&gt; good? That's where hours disappear into tweaking CSS, picking colors, second-guessing layouts, and ultimately settling for something mediocre.&lt;/p&gt;

&lt;p&gt;Google just changed that completely with two tools — &lt;strong&gt;Google Stitch&lt;/strong&gt; and &lt;strong&gt;Google Antigravity&lt;/strong&gt; — and when you combine them, the results are genuinely impressive.&lt;/p&gt;




&lt;h2&gt;
  
  
  What Is Google Stitch?
&lt;/h2&gt;

&lt;p&gt;Google Stitch is a design tool that turns plain text descriptions into complete UI designs for web and mobile apps. Think of it as "vibe designing" — the design equivalent of vibe coding.&lt;/p&gt;

&lt;p&gt;You describe your app idea in plain English, and Stitch generates:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Full wireframes for every screen&lt;/li&gt;
&lt;li&gt;Complete user journeys and navigation flows&lt;/li&gt;
&lt;li&gt;Editable designs you can annotate and modify&lt;/li&gt;
&lt;li&gt;Exportable code for the final designs&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The key thing that sets Stitch apart from just generating a single mockup image is that it &lt;strong&gt;thinks in flows&lt;/strong&gt; — it understands that real apps have multiple screens and designs all of them together, consistently.&lt;/p&gt;

&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.amazonaws.com%2Fuploads%2Farticles%2F7bd7tppegule4evh7kce.webp" 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.amazonaws.com%2Fuploads%2Farticles%2F7bd7tppegule4evh7kce.webp" alt="Google Stitch UI Design Tool" width="800" height="1235"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Google Stitch generating a full set of screens from a single prompt&lt;/em&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  What Is Google Antigravity?
&lt;/h2&gt;

&lt;p&gt;Google Antigravity is an agentic development platform — similar in spirit to Claude Code or Cursor, but built by Google. You describe what you want to build, and Antigravity writes real, working code for it.&lt;/p&gt;

&lt;p&gt;Where it stands out is in its &lt;strong&gt;MCP (Model Context Protocol) support&lt;/strong&gt; — it can connect to external tools and services to extend what it can do. And one of those tools is now Google Stitch.&lt;/p&gt;


&lt;h2&gt;
  
  
  Why Combine Them?
&lt;/h2&gt;

&lt;p&gt;Here's the problem with building UIs using just a coding agent: the agent knows your code, but it has to &lt;em&gt;guess&lt;/em&gt; at good design. It doesn't know your color preferences, your target users, or what visual hierarchy makes sense for your specific app.&lt;/p&gt;

&lt;p&gt;Stitch solves the design problem. Antigravity solves the engineering problem. Together, they solve both — without you having to be a designer or manually bridge the two.&lt;/p&gt;

&lt;p&gt;The workflow looks like this:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Step&lt;/th&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;What Happens&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Antigravity&lt;/td&gt;
&lt;td&gt;Builds initial working app&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Stitch (via MCP)&lt;/td&gt;
&lt;td&gt;Designs beautiful UI for the app&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Antigravity&lt;/td&gt;
&lt;td&gt;Implements the Stitch design into the app&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;You&lt;/td&gt;
&lt;td&gt;Review, refine, ship&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;


&lt;h2&gt;
  
  
  Setting It Up: 3 Steps
&lt;/h2&gt;
&lt;h3&gt;
  
  
  Step 1: Add Google Stitch as an MCP Server in Antigravity
&lt;/h3&gt;

&lt;p&gt;Open Google Antigravity and look for the agent window on the right side. Click the &lt;strong&gt;three dots (ellipses)&lt;/strong&gt; and select &lt;strong&gt;MCP Servers&lt;/strong&gt;. Search for "stitch" and click install.&lt;/p&gt;

&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.amazonaws.com%2Fuploads%2Farticles%2Ft1wpa9et0urbjd6wgzm8.webp" 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.amazonaws.com%2Fuploads%2Farticles%2Ft1wpa9et0urbjd6wgzm8.webp" alt="Adding Stitch MCP Server in Antigravity" width="800" height="409"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Installing the Stitch MCP server inside Google Antigravity&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;This is the same MCP pattern you may have seen with other AI tools — it's becoming the standard way AI agents connect to external capabilities.&lt;/p&gt;
&lt;h3&gt;
  
  
  Step 2: Get a Stitch API Key
&lt;/h3&gt;

&lt;p&gt;Head to &lt;a href="https://stitch.withgoogle.com" rel="noopener noreferrer"&gt;stitch.withgoogle.com&lt;/a&gt; and sign in. Click your &lt;strong&gt;profile picture&lt;/strong&gt; at the top right → &lt;strong&gt;Stitch Settings&lt;/strong&gt; → &lt;strong&gt;Create API Key&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Copy the key and paste it into the MCP server configuration screen back in Antigravity.&lt;/p&gt;

&lt;p&gt;That's it — the two tools are now connected.&lt;/p&gt;
&lt;h3&gt;
  
  
  Step 3: Prompt Away
&lt;/h3&gt;

&lt;p&gt;Now whenever you want Stitch to design something for your app, just mention it in your Antigravity prompt:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Use the Stitch MCP server to design a visual interface for this app
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Antigravity will automatically pass your app's context — what it does, what screens exist, what the data looks like — to Stitch. This is much better than prompting Stitch directly, because Antigravity already knows your entire codebase and can write a far more detailed design brief than you'd write manually.&lt;/p&gt;

&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.amazonaws.com%2Fuploads%2Farticles%2Fi0bmj8bah3ej7oblrs5i.webp" 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.amazonaws.com%2Fuploads%2Farticles%2Fi0bmj8bah3ej7oblrs5i.webp" alt="Antigravity analyzing Signup.tsx and calling Stitch MCP server" width="800" height="497"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Antigravity analyzing the existing Signup.tsx and calling the Stitch MCP server to generate a redesigned UI&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Antigravity automatically reads your existing code, passes the full context to Stitch, and starts generating. You can watch the entire process in real time on the right panel — every MCP tool call, every decision, completely transparent.&lt;/p&gt;




&lt;h2&gt;
  
  
  A Real Example: From Ugly to Impressive
&lt;/h2&gt;

&lt;p&gt;Here's what this looks like in practice. Say you've built a simple app that parses changelogs and shows you what's new with a library — functional, but visually plain.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Before Stitch&lt;/strong&gt; — the default output from Antigravity looks something like this: white background, plain text, basic layout. It works, but it's not something you'd show in a portfolio or share with users confidently.&lt;/p&gt;

&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.amazonaws.com%2Fuploads%2Farticles%2Fapu4t7il3yvmpcxj0zrm.webp" 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.amazonaws.com%2Fuploads%2Farticles%2Fapu4t7il3yvmpcxj0zrm.webp" alt="Before Stitch — Basic App UI" width="800" height="539"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;A functional but visually plain app before applying Stitch designs&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After Stitch&lt;/strong&gt; — Antigravity calls the Stitch MCP server, generates a proper design proposal, then implements it. Antigravity even switches to a better tech stack (React + Tailwind) if it determines that's more suited to rendering the design correctly.&lt;/p&gt;

&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.amazonaws.com%2Fuploads%2Farticles%2F4qk5o0vz3n46nfk4i8xq.webp" 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.amazonaws.com%2Fuploads%2Farticles%2F4qk5o0vz3n46nfk4i8xq.webp" alt="After Stitch — Redesigned App UI" width="800" height="474"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;The same app after Antigravity implemented the Stitch-generated design&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The difference is significant — and the key thing is &lt;strong&gt;you didn't design any of it manually&lt;/strong&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  What Makes This Workflow So Efficient
&lt;/h2&gt;

&lt;p&gt;A few things make this combination genuinely powerful rather than just a gimmick:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Stitch exports HTML/CSS files directly.&lt;/strong&gt; When Antigravity pulls in a Stitch design, it gets actual code files — not just images to interpret. This means it doesn't have to guess how to translate the design into code. The design and the implementation stay in sync.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Antigravity writes the design brief automatically.&lt;/strong&gt; When you ask Antigravity to use the Stitch MCP server, it generates the prompt to Stitch based on your app's actual functionality. This produces much more accurate designs than if you described your app to Stitch yourself from scratch.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You stay in one place.&lt;/strong&gt; The entire workflow — coding, designing, implementing — happens inside Antigravity. You're not switching between four different tools and manually copying things across.&lt;/p&gt;




&lt;h2&gt;
  
  
  Should You Use This?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Yes, if:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You're a developer who struggles with UI design&lt;/li&gt;
&lt;li&gt;You're building a portfolio project and want it to look polished&lt;/li&gt;
&lt;li&gt;You want to prototype and demo an app quickly without hiring a designer&lt;/li&gt;
&lt;li&gt;You already use Google Antigravity for coding&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Maybe not if:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You have a dedicated designer on your team&lt;/li&gt;
&lt;li&gt;You need highly custom, brand-specific design that requires precise control&lt;/li&gt;
&lt;li&gt;You're working on a project that doesn't use web or mobile UI at all&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Honest Take
&lt;/h2&gt;

&lt;p&gt;This isn't magic. The designs Stitch generates are good — genuinely good — but they still benefit from your review and feedback. Think of it as having a junior designer who produces solid first drafts that you then refine, rather than a senior designer who nails it perfectly on the first try.&lt;/p&gt;

&lt;p&gt;But for students and solo developers? That junior designer would have cost you hours of struggling with CSS or money hiring someone on Fiverr. Getting a solid, functional, good-looking UI in a few prompts is a real productivity win.&lt;/p&gt;

&lt;p&gt;The MCP integration is what makes this feel like a glimpse into how AI-powered development will work going forward — specialized tools connected together, each doing what it does best, coordinated by an agent that understands your full context.&lt;/p&gt;




&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;First impressions matter in software just as much as anywhere else. A well-designed UI signals effort, professionalism, and care — even if the underlying logic is identical to a plain-looking app.&lt;/p&gt;

&lt;p&gt;Google Stitch + Antigravity removes the biggest excuse developers have for shipping ugly apps: &lt;em&gt;"I'm not a designer."&lt;/em&gt; Now you don't need to be.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Have you tried Google Stitch or Antigravity? Drop a comment below — would love to hear what you built with it.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>googlestitch</category>
      <category>antigravity</category>
      <category>webdev</category>
      <category>uidesign</category>
    </item>
    <item>
      <title>Claude Code vs Cursor vs Antigravity: Which AI Coding Tool Should You Use in 2026?</title>
      <dc:creator>Akshay Kumar</dc:creator>
      <pubDate>Fri, 20 Mar 2026 03:50:32 +0000</pubDate>
      <link>https://dev.to/akshay0611/claude-code-vs-cursor-vs-antigravity-which-ai-coding-tool-should-you-use-in-2026-k1m</link>
      <guid>https://dev.to/akshay0611/claude-code-vs-cursor-vs-antigravity-which-ai-coding-tool-should-you-use-in-2026-k1m</guid>
      <description>&lt;h1&gt;
  
  
  Claude Code vs Cursor vs Antigravity: Which AI Coding Tool Should You Use in 2026?
&lt;/h1&gt;




&lt;p&gt;Every CS student and developer I know is using at least one AI coding tool right now. The problem isn't finding one — it's figuring out which one is actually worth your time, and whether the paid ones are worth the money.&lt;/p&gt;

&lt;p&gt;I've personally used all three — Claude Code, Cursor, and Google Antigravity — across real projects, not just hello world demos. Here's what I actually think.&lt;/p&gt;




&lt;h2&gt;
  
  
  Quick Overview
&lt;/h2&gt;

&lt;p&gt;Before diving deep, here's the one-line summary of each:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;Best Described As&lt;/th&gt;
&lt;th&gt;Cost&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Claude Code&lt;/td&gt;
&lt;td&gt;AI agent that lives in your terminal&lt;/td&gt;
&lt;td&gt;$20–$200/month&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cursor&lt;/td&gt;
&lt;td&gt;VS Code with AI baked into everything&lt;/td&gt;
&lt;td&gt;Free–$200/month&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Antigravity&lt;/td&gt;
&lt;td&gt;Mission control for autonomous AI agents&lt;/td&gt;
&lt;td&gt;Free (for now)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  Claude Code
&lt;/h2&gt;

&lt;p&gt;Claude Code is Anthropic's agentic coding tool — and it's fundamentally different from what most people picture when they think "AI coding assistant."&lt;/p&gt;

&lt;p&gt;There's no GUI. No sidebar chat. No autocomplete popup. Claude Code runs entirely in your terminal and treats your whole codebase as its working memory. You give it a goal — "add JWT authentication to the API" — and it reads your existing code, makes a plan, implements the changes across multiple files, runs your tests, fixes failures, and reports back when done.&lt;/p&gt;

&lt;p&gt;The key thing that sets it apart is how it handles complex, multi-step work. It doesn't just write code — it thinks through the problem first. Plan Mode shows you the full strategy before anything is touched, which builds a lot of trust.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What works really well:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;200,000 token context window — it actually understands large codebases&lt;/li&gt;
&lt;li&gt;Production-quality output — thorough error handling, proper architecture&lt;/li&gt;
&lt;li&gt;GitHub integration — tag it on a PR and it responds to reviewer comments&lt;/li&gt;
&lt;li&gt;MCP support — connects to external tools including databases, APIs, and more&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;What's not ideal:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Takes longer than the others — it's thorough, not fast&lt;/li&gt;
&lt;li&gt;Terminal-only experience isn't for everyone&lt;/li&gt;
&lt;li&gt;Costs add up quickly during heavy agentic sessions&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing (USD &amp;amp; INR):&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Plan&lt;/th&gt;
&lt;th&gt;USD/month&lt;/th&gt;
&lt;th&gt;INR/month&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Pro&lt;/td&gt;
&lt;td&gt;$20&lt;/td&gt;
&lt;td&gt;₹1,670&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Max 5x&lt;/td&gt;
&lt;td&gt;$100&lt;/td&gt;
&lt;td&gt;₹8,350&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Max 20x&lt;/td&gt;
&lt;td&gt;$200&lt;/td&gt;
&lt;td&gt;₹16,700&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Student tip:&lt;/strong&gt; You can run Claude Code completely free using Ollama with open-source models. We tested this on a MacBook Air — check the full guide here: &lt;a href="https://dev.to/blog/run-claude-code-free-ollama"&gt;Run Claude Code for Free Using Ollama&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Cursor
&lt;/h2&gt;

&lt;p&gt;Cursor is what happens when you take VS Code — already the world's most popular editor — and rebuild it from scratch with AI as a first-class citizen rather than a plugin.&lt;/p&gt;

&lt;p&gt;Everything you already know works. Your extensions, your themes, your keyboard shortcuts, your muscle memory. The only difference is that AI is now woven into every layer of the editor. The autocomplete doesn't just complete the current line — it predicts entire functions based on what you're building. The Agent Mode doesn't just answer questions — it takes over your project, makes changes across files, runs tests, and iterates.&lt;/p&gt;

&lt;p&gt;What makes Cursor stand out is speed. Most tasks complete in under 30 seconds. For rapid prototyping, hackathons, or quick feature work, nothing comes close.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What works really well:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Zero learning curve — productive from minute one&lt;/li&gt;
&lt;li&gt;Fastest output of the three by a significant margin&lt;/li&gt;
&lt;li&gt;Background agents that work while you're doing other things&lt;/li&gt;
&lt;li&gt;Free tier is genuinely useful, not crippled&lt;/li&gt;
&lt;li&gt;Team features are the most mature of the three&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;What's not ideal:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Occasionally takes shortcuts on code quality for the sake of speed&lt;/li&gt;
&lt;li&gt;Context window (128K standard) can struggle on very large codebases&lt;/li&gt;
&lt;li&gt;Background agents send your code to external servers — worth knowing&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing (USD &amp;amp; INR):&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Plan&lt;/th&gt;
&lt;th&gt;USD/month&lt;/th&gt;
&lt;th&gt;INR/month&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Free&lt;/td&gt;
&lt;td&gt;$0&lt;/td&gt;
&lt;td&gt;₹0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pro&lt;/td&gt;
&lt;td&gt;$20&lt;/td&gt;
&lt;td&gt;₹1,670&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Max 5x&lt;/td&gt;
&lt;td&gt;$100&lt;/td&gt;
&lt;td&gt;₹8,350&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Max 20x&lt;/td&gt;
&lt;td&gt;$200&lt;/td&gt;
&lt;td&gt;₹16,700&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  Google Antigravity
&lt;/h2&gt;

&lt;p&gt;Antigravity is the most ambitious tool of the three — and the hardest to explain, because it's genuinely unlike anything most developers have used before.&lt;/p&gt;

&lt;p&gt;The core shift: in Claude Code and Cursor, you are the developer and AI assists you. In Antigravity, AI agents are the developers and you are the orchestrator. You set the goal, the agents figure out how to get there — writing code in the Editor, running commands in the Terminal, and verifying results in a real Browser, all simultaneously.&lt;/p&gt;

&lt;p&gt;The Browser piece is what surprised me most. Antigravity doesn't just write code and hope it works — it actually opens Chrome, navigates your app, takes screenshots, and confirms the feature works before marking the task done. That level of autonomous verification is genuinely impressive.&lt;/p&gt;

&lt;p&gt;The other standout feature is Artifacts — instead of raw code diffs or log files, Antigravity gives you readable task summaries, screenshots, and browser recordings of what the agents did. It's far easier to trust than staring at hundreds of changed lines.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What works really well:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Completely free right now — genuinely powerful at zero cost&lt;/li&gt;
&lt;li&gt;Browser-based verification means fewer "it works on my machine" moments&lt;/li&gt;
&lt;li&gt;MCP support is excellent — works seamlessly with Google Stitch for UI design&lt;/li&gt;
&lt;li&gt;Multi-agent orchestration lets different agents tackle different parts simultaneously&lt;/li&gt;
&lt;li&gt;Artifacts make it easy to review and understand what happened&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;What's not ideal:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Steepest learning curve of the three — the agent-first model takes adjustment&lt;/li&gt;
&lt;li&gt;Still early — some features marked "coming soon"&lt;/li&gt;
&lt;li&gt;Free pricing won't last forever once Team/Enterprise tiers launch&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing (USD &amp;amp; INR):&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Plan&lt;/th&gt;
&lt;th&gt;USD/month&lt;/th&gt;
&lt;th&gt;INR/month&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Public Preview&lt;/td&gt;
&lt;td&gt;Free&lt;/td&gt;
&lt;td&gt;₹0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Team (coming soon)&lt;/td&gt;
&lt;td&gt;TBD&lt;/td&gt;
&lt;td&gt;TBD&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Seen what Antigravity can do with UI?&lt;/strong&gt; We used it with Google Stitch MCP to completely redesign an app's signup page — no design skills needed: &lt;a href="https://dev.to/blog/google-stitch-antigravity-ui-guide"&gt;Build Beautiful App UIs Without Being a Designer&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Direct Comparison
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Speed
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Task&lt;/th&gt;
&lt;th&gt;Cursor&lt;/th&gt;
&lt;th&gt;Antigravity&lt;/th&gt;
&lt;th&gt;Claude Code&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Simple feature&lt;/td&gt;
&lt;td&gt;~2 min&lt;/td&gt;
&lt;td&gt;~5 min&lt;/td&gt;
&lt;td&gt;~10 min&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Complex feature&lt;/td&gt;
&lt;td&gt;~5 min&lt;/td&gt;
&lt;td&gt;~8 min&lt;/td&gt;
&lt;td&gt;~25 min&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Code review&lt;/td&gt;
&lt;td&gt;Instant&lt;/td&gt;
&lt;td&gt;Fast&lt;/td&gt;
&lt;td&gt;Thorough&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Cursor wins on speed. Claude Code wins on quality. Antigravity sits in the middle — slower than Cursor but it verifies its work automatically.&lt;/p&gt;

&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.amazonaws.com%2Fuploads%2Farticles%2Fpeplbozrnvdljc5a62nj.webp" 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.amazonaws.com%2Fuploads%2Farticles%2Fpeplbozrnvdljc5a62nj.webp" alt="Claude Code running via Ollama on MacBook Air" width="800" height="238"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Claude Code v2.1.44 running in terminal — the methodical approach that produces production-quality output&lt;/em&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  Code Quality
&lt;/h3&gt;

&lt;p&gt;Cursor produces clean, working code fast — but occasionally cuts corners. Great for prototypes, needs review before production.&lt;/p&gt;

&lt;p&gt;Claude Code writes like a senior developer who has been through enough production incidents to never skip error handling — thorough, well-architected, and heavily commented. Takes longer but saves debugging time later.&lt;/p&gt;

&lt;p&gt;Antigravity produces solid, well-structured code. Occasionally overengineers simple solutions, but the browser verification means what you get actually works end-to-end.&lt;/p&gt;




&lt;h3&gt;
  
  
  Codebase Understanding
&lt;/h3&gt;

&lt;p&gt;Claude Code's 200,000 token context window is the largest of the three — it can hold your entire codebase in memory at once. Ask it "why are users seeing slow load times?" and it'll analyze your database queries, API calls, and rendering logic together. Context stays consistent throughout long sessions.&lt;/p&gt;

&lt;p&gt;Cursor uses semantic search — it doesn't need your exact words to find relevant code. Ask "where do we handle payment failures?" and it finds the right files even if they're named something different. Excellent for navigating unfamiliar codebases quickly.&lt;/p&gt;

&lt;p&gt;Antigravity builds a knowledge base over time. After a few sessions it starts remembering your preferred patterns and conventions without being told. The most promising approach long-term, but the least mature right now.&lt;/p&gt;




&lt;h3&gt;
  
  
  For Students and Budget Developers
&lt;/h3&gt;

&lt;p&gt;This is where it gets practical.&lt;/p&gt;

&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.amazonaws.com%2Fuploads%2Farticles%2Fgg5ujk08kxio8chjlmqy.jpeg" 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.amazonaws.com%2Fuploads%2Farticles%2Fgg5ujk08kxio8chjlmqy.jpeg" alt="Claude Code + Ollama — 100% Local, 100% Free" width="800" height="800"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Running Claude Code free with Ollama — the best option for students on a budget&lt;/em&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Situation&lt;/th&gt;
&lt;th&gt;Best Choice&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Zero budget&lt;/td&gt;
&lt;td&gt;Antigravity (free) + Cursor free tier&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hackathon&lt;/td&gt;
&lt;td&gt;Cursor Pro (₹1,670/month)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Final year project&lt;/td&gt;
&lt;td&gt;Claude Code or Antigravity&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Learning to code&lt;/td&gt;
&lt;td&gt;Cursor (familiar IDE)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Internship / job prep&lt;/td&gt;
&lt;td&gt;Claude Code (production quality)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Running Claude Code free&lt;/td&gt;
&lt;td&gt;Claude Code + Ollama&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  My Honest Take
&lt;/h2&gt;

&lt;p&gt;After using all three across real projects, here's where I actually land:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Antigravity is the best starting point for students right now&lt;/strong&gt; — it's free, it's powerful, and using it teaches you the agent-first model that's going to define how software gets built going forward. The fact that it's free won't last forever, so take advantage of this window.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cursor is the best all-rounder&lt;/strong&gt; — the free tier is genuinely useful, the Pro plan at ₹1,670/month is the most accessible paid option, and the speed makes it ideal for rapid work. If you can afford one paid tool, this is the one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Claude Code is the best for serious work&lt;/strong&gt; — when code quality actually matters, when you're building something production-grade, when you need an AI that thinks deeply rather than acts fast. Pair it with Ollama if budget is a concern.&lt;/p&gt;

&lt;p&gt;The good news? You don't have to pick just one. Many developers use Cursor for day-to-day speed, Claude Code for complex tasks, and Antigravity for experimental projects. They solve slightly different problems and work well together.&lt;/p&gt;




&lt;h2&gt;
  
  
  Three Questions Before You Commit
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Privacy:&lt;/strong&gt; All three send your code to external servers. For sensitive or proprietary projects, are you comfortable with that? This matters more than people admit.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Dependency:&lt;/strong&gt; These are cloud services. What happens when they go down during a critical deadline? Having a fallback plan is worth thinking about.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Your fundamentals:&lt;/strong&gt; The developers who get the most out of these tools are the ones who understand what's happening under the hood. Use AI to go faster — not as a substitute for understanding what you're building.&lt;/p&gt;




&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;The question in 2026 isn't whether to use AI coding tools. It's which ones match how you actually work.&lt;/p&gt;

&lt;p&gt;Speed and familiarity — Cursor. Depth and code quality — Claude Code. The future of agentic development at zero cost — Antigravity.&lt;/p&gt;

&lt;p&gt;Pick one, go deep, and figure out where it actually fits. That's worth more than jumping between all three without mastering any of them.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Which one are you using? Drop a comment below — would love to know what's working for developers and students in the EduLinkUp community.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>claudecode</category>
      <category>cursor</category>
      <category>antigravity</category>
      <category>aitools</category>
    </item>
    <item>
      <title>Run Claude Code for Free Using Ollama (No API Bill, No Compromise)</title>
      <dc:creator>Akshay Kumar</dc:creator>
      <pubDate>Mon, 02 Mar 2026 04:15:55 +0000</pubDate>
      <link>https://dev.to/akshay0611/run-claude-code-for-free-using-ollama-no-api-bill-no-compromise-5hfm</link>
      <guid>https://dev.to/akshay0611/run-claude-code-for-free-using-ollama-no-api-bill-no-compromise-5hfm</guid>
      <description>&lt;p&gt;If you've been using &lt;strong&gt;Claude Code&lt;/strong&gt; — Anthropic's powerful agentic coding tool — you already know how good it is. The problem? The API bills can add up fast, especially if you're a student, indie developer, or just someone experimenting. A small team can easily burn through hundreds of dollars a month.&lt;/p&gt;

&lt;p&gt;Here's the good news: &lt;strong&gt;you don't have to pay a single rupee to use Claude Code anymore.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Thanks to a recent update in Ollama (v0.14.0+), Claude Code now supports local and cloud open-source models out of the box. No hacks, no fragile adapters — just a clean, simple setup. This guide will walk you through everything, from installation to running your first AI-assisted coding session, completely free.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Quick note:&lt;/strong&gt; If you've been exploring self-hosted AI tools, you might already be familiar with &lt;a href="https://www.edulinkup.dev/blog/run-claude-code-free-ollama" rel="noopener noreferrer"&gt;Moltbot (formerly OpenClaw)&lt;/a&gt; — a free, self-hosted AI assistant. This guide takes a similar philosophy — powerful AI, zero cloud cost — but focused entirely on your coding workflow.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  What Changed? Why This Works Now
&lt;/h2&gt;

&lt;p&gt;Older guides for connecting Claude Code to non-Anthropic models were messy — requiring custom wrappers, brittle API shims, and constant maintenance. Every update risked breaking your setup.&lt;/p&gt;

&lt;p&gt;That's changed. &lt;strong&gt;Ollama now speaks the Anthropic Messages API format natively.&lt;/strong&gt; This means Claude Code can talk to any Ollama model the same way it talks to Anthropic's servers — no middle layer, no workarounds.&lt;/p&gt;

&lt;p&gt;What you gain by going local or using free cloud tiers:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Cost:&lt;/strong&gt; Local models are completely free. Some cloud alternatives cost up to 98% less than Claude Opus.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Privacy:&lt;/strong&gt; Your code never leaves your machine.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Speed:&lt;/strong&gt; No network round trips when running locally.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Flexibility:&lt;/strong&gt; Switch between models without changing your workflow.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Before You Begin: Does Your Machine Qualify?
&lt;/h2&gt;

&lt;p&gt;This is the most important section to read before diving in. Local LLMs are hungry for RAM.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;RAM Available&lt;/th&gt;
&lt;th&gt;What You Can Run&lt;/th&gt;
&lt;th&gt;Experience&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;8 GB&lt;/td&gt;
&lt;td&gt;Very small models only&lt;/td&gt;
&lt;td&gt;Not recommended for coding&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;16 GB&lt;/td&gt;
&lt;td&gt;Small models (7B–14B)&lt;/td&gt;
&lt;td&gt;Rough — expect slow edits and retries&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;32 GB&lt;/td&gt;
&lt;td&gt;Mid-size models (24B–30B)&lt;/td&gt;
&lt;td&gt;Good — comfortable for daily use&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;64 GB+&lt;/td&gt;
&lt;td&gt;Large models (30B–70B)&lt;/td&gt;
&lt;td&gt;Excellent — near-Claude quality&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;The honest truth:&lt;/strong&gt; If you have 16 GB RAM, local models will work but can feel sluggish for real coding tasks — more wrong edits, more retries. At 32 GB (Apple Silicon unified memory or PC RAM), it becomes genuinely productive. Below that, the free &lt;strong&gt;cloud model options&lt;/strong&gt; covered later in this guide are a better bet.&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 1: Install Claude Code
&lt;/h2&gt;

&lt;p&gt;First, you need Claude Code installed on your system.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;macOS / Linux / WSL:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-fsSL&lt;/span&gt; https://claude.ai/install.sh | bash
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Windows (PowerShell):&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;irm&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nx"&gt;https://claude.ai/install.ps1&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;|&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;iex&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Windows (CMD):&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;curl -fsSL https://claude.ai/install.cmd -o install.cmd &amp;amp;&amp;amp; install.cmd &amp;amp;&amp;amp; del install.cmd
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Step 2: Install Ollama
&lt;/h2&gt;

&lt;p&gt;Ollama is what makes this whole setup possible. It runs open-source models locally and now speaks Claude Code's language natively.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-fsSL&lt;/span&gt; https://ollama.com/install.sh | sh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Once installed, Ollama runs as a background service on &lt;code&gt;http://localhost:11434&lt;/code&gt;.&lt;/p&gt;

&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.amazonaws.com%2Fuploads%2Farticles%2F2pcnz0w270hn0f619obg.jpeg" 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.amazonaws.com%2Fuploads%2Farticles%2F2pcnz0w270hn0f619obg.jpeg" alt="Ollama — run open-source models locally while keeping your data safe" width="800" height="456"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Ollama — the easiest way to run open-source models locally while keeping your data safe&lt;/em&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  Step 3: Pick and Pull a Model
&lt;/h2&gt;

&lt;p&gt;This is where your RAM decides what you can run. Pull the model that matches your machine:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Great starting point for 32 GB machines&lt;/span&gt;
ollama pull devstral-small-2

&lt;span class="c"&gt;# Stronger coding ability, still works on 32 GB&lt;/span&gt;
ollama pull qwen3-coder:30b

&lt;span class="c"&gt;# Good speed-to-quality tradeoff (quantized, lighter)&lt;/span&gt;
ollama pull glm4.7-flash:q8_0
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Model cheat sheet by RAM:&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;RAM&lt;/th&gt;
&lt;th&gt;Recommended Model&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;16 GB&lt;/td&gt;
&lt;td&gt;&lt;code&gt;glm4.7-flash:q8_0&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Quantized, lighter footprint&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;32 GB&lt;/td&gt;
&lt;td&gt;&lt;code&gt;devstral-small-2&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Best balance of speed + quality&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;32 GB (prefer quality)&lt;/td&gt;
&lt;td&gt;&lt;code&gt;qwen3-coder:30b&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Better output, slightly slower&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;64 GB+&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;qwen3-coder:30b&lt;/code&gt; or larger&lt;/td&gt;
&lt;td&gt;Comfortable at full precision&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Tip:&lt;/strong&gt; For coding tasks, always use a model that supports at least &lt;strong&gt;64k tokens context length&lt;/strong&gt;. Shorter context means Claude Code loses track of your codebase mid-session.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  Step 4: Connect Ollama to Claude Code
&lt;/h2&gt;

&lt;p&gt;Now the magic part. You just need to set two environment variables to point Claude Code at Ollama instead of Anthropic's servers.&lt;/p&gt;

&lt;p&gt;Add these to your &lt;code&gt;~/.zshrc&lt;/code&gt; or &lt;code&gt;~/.bashrc&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;export &lt;/span&gt;&lt;span class="nv"&gt;ANTHROPIC_AUTH_TOKEN&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"ollama"&lt;/span&gt;
&lt;span class="nb"&gt;export &lt;/span&gt;&lt;span class="nv"&gt;ANTHROPIC_BASE_URL&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"http://localhost:11434"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then reload your shell:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;source&lt;/span&gt; ~/.zshrc
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Run Claude Code with your local model:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;claude &lt;span class="nt"&gt;--model&lt;/span&gt; devstral-small-2
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That's it. You're now running Claude Code completely free, on your own machine.&lt;/p&gt;

&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.amazonaws.com%2Fuploads%2Farticles%2Fpeplbozrnvdljc5a62nj.webp" 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.amazonaws.com%2Fuploads%2Farticles%2Fpeplbozrnvdljc5a62nj.webp" alt="Claude Code v2.1.44 running successfully via glm-4.7:cloud on a MacBook Air" width="800" height="238"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Claude Code v2.1.44 running successfully via glm-4.7:cloud on a MacBook Air — no local GPU needed&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Alternatively, Ollama has a shortcut command that skips the manual env setup:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ollama launch claude &lt;span class="nt"&gt;--model&lt;/span&gt; devstral-small-2
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This auto-wires everything. Great for a quick start.&lt;/p&gt;




&lt;h2&gt;
  
  
  Don't Have 32 GB RAM? Use Free Cloud Models
&lt;/h2&gt;

&lt;p&gt;If your machine doesn't meet the RAM bar for local models, Ollama has a clever trick: &lt;strong&gt;&lt;code&gt;:cloud&lt;/code&gt; variants&lt;/strong&gt;. These run on Ollama's cloud infrastructure but use the exact same CLI commands as local models. No separate API keys to manage.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pull a cloud model:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ollama pull glm-4.7:cloud
ollama pull minimax-m2.1:cloud
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Run it:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;claude &lt;span class="nt"&gt;--model&lt;/span&gt; glm-4.7:cloud
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Same workflow, no local GPU required. Ollama's free tier has usage limits, but for students and casual coders it's more than enough for regular sessions.&lt;/p&gt;




&lt;h2&gt;
  
  
  Using Ollama with the Anthropic SDK (For Developers)
&lt;/h2&gt;

&lt;p&gt;If you're building apps with the Anthropic SDK, switching to Ollama is just a one-line change — swap the &lt;code&gt;base_url&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Python:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;anthropic&lt;/span&gt;

&lt;span class="n"&gt;client&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;anthropic&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Anthropic&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="n"&gt;base_url&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="s"&gt;http://localhost:11434&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;api_key&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="s"&gt;ollama&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;  &lt;span class="c1"&gt;# required field, but ignored by Ollama
&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="n"&gt;message&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;client&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;messages&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;create&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="n"&gt;model&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="s"&gt;qwen3-coder&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;messages&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;[{&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="s"&gt;role&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="s"&gt;user&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="s"&gt;content&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="s"&gt;Write a function to check if a number is prime&lt;/span&gt;&lt;span class="sh"&gt;'&lt;/span&gt;&lt;span class="p"&gt;}]&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;message&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;content&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;].&lt;/span&gt;&lt;span class="n"&gt;text&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;JavaScript:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nx"&gt;Anthropic&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;@anthropic-ai/sdk&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;anthropic&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Anthropic&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="na"&gt;baseURL&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;http://localhost:11434&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;apiKey&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;ollama&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;})&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;message&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;anthropic&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;messages&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;create&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="na"&gt;model&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;qwen3-coder&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;messages&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[{&lt;/span&gt; &lt;span class="na"&gt;role&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;user&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;content&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Write a function to check if a number is prime&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;}],&lt;/span&gt;
&lt;span class="p"&gt;})&lt;/span&gt;

&lt;span class="nx"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;message&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;content&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;].&lt;/span&gt;&lt;span class="nx"&gt;text&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Your existing Anthropic-based apps will work with Ollama models with zero other changes.&lt;/p&gt;




&lt;h2&gt;
  
  
  What Features Does Claude Code Still Support?
&lt;/h2&gt;

&lt;p&gt;You might wonder if going local means losing features. Here's what works with Claude Code + Ollama:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Feature&lt;/th&gt;
&lt;th&gt;Supported?&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Multi-turn conversations&lt;/td&gt;
&lt;td&gt;✅ Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Streaming responses&lt;/td&gt;
&lt;td&gt;✅ Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;System prompts&lt;/td&gt;
&lt;td&gt;✅ Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Tool / function calling&lt;/td&gt;
&lt;td&gt;✅ Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Extended thinking&lt;/td&gt;
&lt;td&gt;✅ Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Vision (image input)&lt;/td&gt;
&lt;td&gt;✅ Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The full feature set is there. The only real trade-off is model quality versus the flagship Claude Opus — which we address below.&lt;/p&gt;




&lt;h2&gt;
  
  
  Honest Performance Expectations
&lt;/h2&gt;

&lt;p&gt;Let's be real about what you can expect, because this guide won't sugar-coat it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On a MacBook Pro M1 with 32 GB RAM:&lt;/strong&gt;&lt;br&gt;
&lt;code&gt;devstral-small-2&lt;/code&gt; (24B) runs at an acceptable speed for daily tasks. &lt;code&gt;qwen3-coder:30b&lt;/code&gt; works but is noticeably slower — not ideal for quick iterations.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On a machine with 16 GB RAM:&lt;/strong&gt;&lt;br&gt;
Expect slower responses and occasional wrong edits that require re-prompting. The &lt;code&gt;:cloud&lt;/code&gt; variants from Ollama will serve you better.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Quality vs Claude Opus:&lt;/strong&gt;&lt;br&gt;
Open-source models at the 24B–30B range are genuinely impressive for routine coding — boilerplate, refactoring, debugging, writing tests. For complex architectural decisions or tricky algorithms, Claude Opus still has an edge. The free setup is not a perfect replacement, but for everyday coding tasks, it gets the job done.&lt;/p&gt;




&lt;h2&gt;
  
  
  Choosing the Right Setup for You
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Your Situation&lt;/th&gt;
&lt;th&gt;Best Option&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;32 GB+ RAM, privacy-conscious&lt;/td&gt;
&lt;td&gt;Local model via Ollama&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Under 16 GB RAM&lt;/td&gt;
&lt;td&gt;Ollama cloud model (free tier)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Want free + no setup&lt;/td&gt;
&lt;td&gt;&lt;code&gt;ollama launch claude --model glm-4.7:cloud&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Building apps with Anthropic SDK&lt;/td&gt;
&lt;td&gt;Swap &lt;code&gt;base_url&lt;/code&gt; to Ollama (Python/JS example above)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Need the absolute best quality&lt;/td&gt;
&lt;td&gt;Claude Opus via official API (paid)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  A Note on What This Setup Is (and Isn't)
&lt;/h2&gt;

&lt;p&gt;This guide solves the &lt;strong&gt;cost problem&lt;/strong&gt; for Claude Code. It's ideal for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Students learning to code&lt;/li&gt;
&lt;li&gt;Indie developers prototyping ideas&lt;/li&gt;
&lt;li&gt;Anyone who wants to experiment without worrying about credits&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It's &lt;strong&gt;not&lt;/strong&gt; for you if:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You need production-grade AI assistance at scale&lt;/li&gt;
&lt;li&gt;Your tasks regularly require Opus-level reasoning&lt;/li&gt;
&lt;li&gt;You want zero setup and don't mind paying&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For those use cases, the official Anthropic API is still worth it. But for the rest of us? This free setup is a game-changer.&lt;/p&gt;




&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;Claude Code is one of the best agentic coding tools out there. The fact that you can now run it completely free — either locally on your own hardware or through Ollama's free cloud tier — is a massive win for students and developers on a budget.&lt;/p&gt;

&lt;p&gt;The setup literally takes five minutes. Install Claude Code, install Ollama, pull a model, set two environment variables. That's the whole thing.&lt;/p&gt;

&lt;p&gt;If you enjoyed this and want to explore more free self-hosted AI tools, check out our guide on &lt;strong&gt;&lt;a href="https://www.edulinkup.dev/blog/run-claude-code-free-ollama" rel="noopener noreferrer"&gt;Moltbot — a free, self-hosted AI assistant&lt;/a&gt;&lt;/strong&gt; that runs on a $5/month VPS and connects to WhatsApp, Telegram, and more.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Have a model recommendation or a setup that works great on your machine? Drop a comment below — the community would love to hear it.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ollama</category>
      <category>claudecode</category>
      <category>ai</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
