How to Get Started with GitWit and Where to Find Learning Resources

Updated

You can start using GitWit by going to gitwit.dev and selecting the Start Building entry point, which takes you into a browser-based IDE where you write code directly in your browser. GitWit is an open-source, AI-native coding platform that lets you build, test, and deploy with AI-powered suggestions and real-time collaboration. The platform is aimed at developers who want to move from idea to working project quickly, and it includes a full backend built into your Next.js app. If you prefer to learn by watching before you build, GitWit also publishes walkthroughs, live coding sessions, and a setup tutorial for AWS.

What you need before you start

  • A modern browser. The IDE runs in the browser, so no local editor install is required to begin.
  • A project idea or an existing Next.js app you want to work on.
  • Optional but useful: a GitHub account, since GitWit integrates with GitHub.
  • Optional: a Discord account if you want community help.

Step-by-step: getting started

  1. Open gitwit.dev. The homepage presents the platform as "AI coding for the next generation of developers" and offers a Start Building button.
  2. Select Start Building. This is the documented entry point into the product. Expect to land in the browser-based IDE.
  3. Write code in the browser IDE. The editor supports syntax highlighting, auto-completion, and other features you would expect from a desktop IDE.
  4. Use AI-powered assistance as you go. Suggestions appear while you build, test, and deploy.
  5. Connect GitHub if you want version control and collaboration. GitHub integration is listed as a core feature.
  6. Build your backend inside your Next.js app. GitWit's browser-based IDE is described as having a full backend seamlessly built into your Next.js app, so full-stack work happens in the same environment.
  7. Collaborate in real time. Real-time collaboration is part of the core workflow, which matters if you are pairing or working with a team.

Expected result: you have a running project in the browser IDE, with AI suggestions available and GitHub connected if you chose to link it.

Learning resources available

Resource What it covers Where to find it
GitWit Walkthrough (Feb 11, 2025) A comprehensive walkthrough of GitWit's features and capabilities, framed around accelerating your development workflow with AI-powered coding Content section on gitwit.dev
Building GitWit Live Streams (Apr 27, 2024) Live coding sessions and weekly GitWit Sync meetings where the team builds and improves GitWit in real time Content section on gitwit.dev
Setting up GitWit on AWS (May 10, 2024) Step-by-step guide to deploying GitWit on AWS Content section on gitwit.dev
YouTube live streams Weekly live streaming, per the site's "Build with Us" section YouTube, linked from gitwit.dev
Discord community Help and discussion with other users and contributors Join Discord community link on gitwit.dev
GitHub repository Source code, issues, and contribution entry points Star on GitHub link on gitwit.dev

Common sticking points

  • Confusing "start building" with "install locally." The documented first step is the browser IDE, not a local setup. Local or cloud deployment is a separate path covered by the AWS tutorial.
  • Skipping the walkthrough. The Feb 11, 2025 walkthrough is the most direct feature tour; watching it first saves trial-and-error in the IDE.
  • Assuming you need to be a Next.js expert. GitWit builds a backend into your Next.js app, but the platform is positioned for building ideas in minutes, so the intended starting point is a project idea rather than deep framework knowledge.
  • Missing the weekly cadence. Live streams and GitWit Sync meetings happen weekly, so if you want to follow development or ask questions live, check the schedule rather than assuming on-demand content only.

Who this fits

GitWit suits developers who want an AI-assisted, browser-first workflow with GitHub integration and a built-in Next.js backend, and who value an open-source project they can follow or contribute to. If you need a fully offline, local-only editor, or you are not working with Next.js, the fit is weaker — the documented backend integration is specifically into Next.js apps.