GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (67%)
• Sign in (25%)
• Errors (8%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Antananarivo	Website Down	10 hours ago
Paris	Sign in	5 days ago
Lure	Website Down	9 days ago
Ashkelon	Website Down	10 days ago
Veigné	Errors	19 days ago
Paris	Website Down	22 days ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Eric Vya (@ericvyacheslav) reported 5 minutes ago

  🚨 Someone just open sourced a way to run a 744B param model on a normal gaming PC. It's called Colibrì. Think of it as llama.cpp, but built to treat your GPU, RAM, and SSD as one shared memory pool instead of needing enough VRAM to hold the whole model. Here's what it does: → Runs GLM-5.2, a 744B-parameter MoE model, by streaming experts straight from disk instead of loading them all into VRAM → Pure C, zero engine dependencies → Ships a live web dashboard showing token speed and which of the 19,456 experts just fired → Never silently drops model precision when memory runs tight, it just slows down → Works across consumer and mixed hardware, not one fixed GPU tier 21K+ GitHub stars. Apache 2.0 license. 100% Open Source. (Link in the reply)

• 
  Lukas Hermann (@_lhermann) reported 8 minutes ago

  @DmytroKrasun How do you sponsor? Github? OpenCollective? I did though GitHub for a while but they don't issue invoices which was quite a headache for me.

• 
  Jens Kuerschner (@jekuer) reported 8 minutes ago

  @_lhermann @DmytroKrasun Had a similar issue with GitHub Copilot. Not usable therefore. But for Sponsors, can't you just write the invoice yourself, since you are invoicing GitHub?

• 
  Ndianabasi Udonkang (@_ndianabasi) reported 8 minutes ago

  I woke up 4:30AM yesterday and had this rare motivation to re-attempt something I have done twice already and failed: migration of the build system of the old codebase for Gotedo Vineyard from Webpack to Vite. The codebase goes back to 2019 when I started work on the Gotedo Platform. Technologies have started, matured, and even demised over the last 7 years but the build system for the codebase remained the same. The result is a slow and painful development and production build workflow. Before the migration, the average build time in our continuous integration pipeline was 11 minutes. This isn't just expensive in terms of time value, it is also expensive in monetary value as we have to spend a lot of GitHub CI minutes building the codebase during releases. So, yesterday, I opted to work with Grok. I told it what I wanted to do, shared all the config files, and we went through several rounds of discussions and agree on an action plan for the migration from Webpack + Babel to Vite. The codebase still uses Vue 2 (a deprecated version of Vuejs) and component system from Quasar v1 (also deprecated). Quasar v1 does not support Vite. So the most important work Grok did for me was writing an auto-import plugin for Vite which auto-imports all Quasar components and directives - a crucial functionality needed for optimal development experience. The plugin replaced the Quasar's auto-import feature which worked seamlessly with Webpack. I was able to restore all the functionalities in the legacy Vue and Webpack config files including the injection of pre-caching manifest and installation of the service worker for the codebase. At the end of the migration, production deployment time dropped from average of 11 minutes to average of 5 minutes - an about 55% reduction in deployment time. Development builds are now lightning fast. The only outstanding issue after the migration is the Hot Module Reload system which reloads the entire page instead of performing a differential update of affected components. I will address this in later iterations. Total time for migration was 8 hours. The next huge migration task will be the migration to Vue 3. With over 200 Vue components in the codebase, this will be great undertaking. I must admit that without Grok's assistance, I'm not sure I would have completed the migration. Maybe I would have failed once again. This is one of the benefits of AI where it can used to unblock tasks when would have been very difficult to accomplish. In case you are wondering how I use AI for coding. I don't use coding agents. I manually prompt over a chat interface, read through provided solutions, fine-tune were needed before applying the solutions to our code bases. I still do a lot of manual coding as I have to careful integrate and clean up the solutions from AI systems. So, our codebases are still as carefully and beautifully crafted as they were before AI assistance. All glory goes to God.

• 
  RetroChainer (@RetroChainer) reported 8 minutes ago

  KARPATHY POSTED 800 WORDS ON GITHUB AND SHOWED DEVS THEY'D BEEN USING AI AT 5 PERCENT. that graph in the clip is one vault claude built and linked by itself - thousands of notes, every connection drawn automatically. the idea is stupid simple. your files are source code. a wiki is the compiled build. you don't recompile a program every time you run it. so stop making ai reread your raw files every single session. karpathy called it the llm wiki. the gist crossed 5,000 forks in days. the whole system is three folders. raw/ is every source you drop in: pdfs, transcripts, highlights, voice memos. you never edit these. wiki/ is where claude compiles clean pages: one concept each, summary, key points, [[wikilinks]], sources. plus an index and a hot-cache file so it knows where to look first. instructions/ is the rules it compiles by: one concept per page, flag contradictions instead of overwriting, mark a page stale after 90 days. the stack is boring on purpose. claude desktop, obsidian free and local, one mcp connector to the vault. nothing else. feed it one document and claude turns it into 8-15 linked pages, each shorter than the original. every future question reads that clean layer, never the raw file again. the math is the quiet part. 50 docs at 5,000 tokens each is 250k raw. the old way reloads all of them every query: 500k to 1m tokens a day, on the same files, forever. the wiki way pays 250k once, then 5-15k per query. the guide clocks it at 70-90% fewer tokens, and it compounds as the vault grows. no database, no cloud service, no subscription past claude. the uncomfortable part isn't that it saves tokens. it's that every ai tool you touch forgets you every 24 hours by design, and the fix was always an architecture you could build in an afternoon. follow @RetroChainer for more systems where one person outbuilds a whole team, and bookmark this so you can build your wiki before everyone else does.

• 
  Kingmaxx22🕹️🔖 (@22Kingmaxx) reported 10 minutes ago

  @Double2MC @sophiiess_ yes this is the real issue making a website that links to a major release on github isn't that complicated

• 
  polymorpheus (@polymorph3us) reported 11 minutes ago

  @cassidoo Better PR review UX. GitHub has not meaningfully adapted to the agentic era. Two big problems remain: 1. Agents write bigger PRs than humans. 2. Agents submit PRs more often than humans.

• 
  EcoCitizenz (@EcoCitizenz) reported 11 minutes ago

  5/8 We built a free GitHub App to check supported committed files for this kind of MCP and agent configuration drift. It reports path-specific findings and remediation guidance. It does not execute repository code. It does not certify the MCP server. It does not sell a passing result.

• 
  Milady (@onchainmilady) reported 14 minutes ago

  HOW IS THIS EVEN POSSIBLE? FREE ACCESS TO EVERY LLM IN THE WORLD AND 100% PRIVATE? Someone posted an HTML file on the Github, and my brain can't comprehend what it does: > Free access to Claude, Grok, Gemini and Chat GPT > You ask one question and get 4 responses > Runs in your browser, no subscription, login or whatever I am leaving the link below, but not sure how legal this is, because this is too cool

• 
  DEVICE_EMPLOYEE (@TheEmployee2108) reported 16 minutes ago

  @SternabR6 @sophiiess_ Yes I'm exaggerating a bit here, but this is how it would seem to any non-dev that's been tricked into clicking on a github link. No it's not a github issue, but github's UI was NOT designed for the average user either way.

• 
  Luella (@luellarocker) reported 18 minutes ago

  CLAUDE DESIGN JUST BECAME THE FRONT DOOR OF CLIENT WORK. anthropic labs dropped a canvas where claude design builds prototypes from a prompt while claude code + github close the loop ➔ the stack claude design = client approval claude code = implementation github = proof + handover ➔ what actually changed design system lives in the repo /design-sync pulls real components handoff to claude code keeps the same ui not a screenshot rebuild ➔ most people still mock in one tool rebuild in another argue in email forever this pipeline ships prototypes share links prs and acceptance artifacts ➔ keywords that matter claude design · claude code · github actions anthropic labs · design system · client work production pipeline · mockups · auto-fix

• 
  Gaston Levai (@gastonelevai) reported 21 minutes ago

  @GRAZZLEYNFT @elGodric After also the community address the issue with the OG dev he finally redirected the fees to the GitHub of @PrJulienMartin .

• 
  Dorian Smiley (@dsmiley411) reported 24 minutes ago

  This is categorically wrong and misunderstands the current state of AI coding. I'm surprised because Chamath is usually on point. AI is often better at expanding architecture than constraining it. It generates plausible abstractions faster than it can establish whether they are necessary. Just like humans. I am convinced the bias comes from GitHub where most of the code is garbage written by devs who are not working in a structured engineering environment. More code means more state combinations, more tests, more failure modes, and more operational burden. In other words not only do the make the same category of errors, they compound them at a speed that bogles the mind. Without guard rails both humans and AI can collapse your codebase, one just does it faster. We recently published an article that details the slop AI produces when attempting complex engineering tasks, link in comments.

• 
  Easy_weezy (@Easy__Weezy) reported 27 minutes ago

  Happy Friday Guys, its morning and here i am trying to fork Vurie Buddy on @CNPYNetwork As i ran into this error as i would need to make some clones on Github and then be able to load it on Canopy, lets see how it goes? As canopy gives us the ability to be able to build our own sovereign chains as well as monetize on their testnet. It is no wonder it is getting all the tractions at the moment. Have you invested in any project yet?

• 
  Sam Parton (@ItsMrSammeh) reported 29 minutes ago

  @github Can you please investigate the issue where some “wp……” js file hangs when loading GitHub. Meaning every request that doesnt hit that cache(usually after 30 mins or so) takes probably about 3 mins to load and multiple refreshes? It’s been going on for months and is driving memad

• 
  jayesh (@wjayesh) reported 30 minutes ago

  @ajs6888 @composio yeah, it was surprising to me too. the tasks are built from the failure modes we see quite often in our production data. these are knowledge work tasks across apps like github, slack, datadog, etc. one reason why codex is lower on the success is also because it was slow and hit the 900s timeout

• 
  ⚡Tech Momentum⚡ (@TechMomentum_) reported 31 minutes ago

  Anthropic quietly gave Claude Code a real browser. Not a screenshot tool, a tabbed pane inside the app that the agent reads, clicks, and navigates on its own. Ctrl+Shift+B (Cmd+Shift+B on Mac) opens it. Ask Claude Code to check a library's docs, click through your own signup flow, or read a GitHub issue thread, and it just does it. No copy-pasting URLs into chat. Two guardrails keep it from going rogue: a classifier reviews every write action, and there's a domain allowlist outside Auto and Bypass modes. OpenAI shut its own browser tool down earlier this year. Anthropic went the other direction. If your agent still can't open a webpage on its own, that's not a limitation anymore. That's a setup problem.

• 
  Gro-Tsen (@gro_tsen) reported 31 minutes ago

  So, I discovered I could no longer push to GitHub using ssh because my ssh agent just so happens to have a 1024-bit DSA key in store (this is ❊not❊ my GitHub key, and in fact it's probably not used anywhere any more), and GitHub's ssh server is so “offended” at being offered …

• 
  Andrew Okiemute (@AndrewOkiemute) reported 42 minutes ago

  🚨 Just got an email. AI companies are still urgently hiring. Some of these roles have 100+ openings: • Open Source Contributors • Senior Software Engineers • GitHub Contributors • Frontend Engineers • Supply Chain Specialists • Management Consultants • Software Engineers (Go/Python/TS) • Microbiologists The AI hiring wave isn't slowing down. If you have any of these skills, this is your signal to stop watching and start applying. Repost this so someone who needs a job sees it before the weekend. 🔁

• 
  Edd Gorenstein 🧩✡️🏴󠁧󠁢󠁥󠁮󠁧󠁿🆒🥛 (@EddGorenstein) reported 42 minutes ago

  @V33V33V33V33V33 @CryptoCyberia I will continue to pronounce it "Gith-ub" until they fix this. @github

• 
  ✦︎ Expilon ✦︎ (@spikeisms) reported 46 minutes ago

  @TribunalSimp @libanan__2 @AnimeSerbia well yeah thats the issue with using github as your main source for hosting downloads. it's programmer and engineer centric so the code aspects are highlighted over user download. the issue falls on devs not using their FREE website hosting to make a friendly download

• 
  Keyman (@KeyTheMan0) reported 48 minutes ago

  @Gr0tttt @ZipperArtz Only problem is that a lot of people post their videogame mods and simple applications everyone can use on github and forget to make the download more obvious. The avarage mod enjoyer doest code, he barely even uses github

• 
  Med (@medhansh) reported 49 minutes ago

  How to make every Mac, server & cloud worker you own feel like one computer: ====== NETWORKING ====== - Tailscale: Connects all your machines into one private network. SSH into your home desktop from anywhere with no port forwarding and nothing exposed publicly - Thunderbolt Bridge: Connects two nearby Macs directly through a Thunderbolt cable. You get tens of Gbps and sub-ms latency without buying networking gear - 2.5/10GbE: The wired alternative when Thunderbolt isn’t practical. Use it when normal gigabit networking becomes the bottleneck - Cloudflare Tunnel: Gives a local service a public URL without opening a port on your router. Useful for websites, APIs and dashboards other people need to reach - ngrok: Creates a temporary public URL in seconds. Perfect for testing webhooks against something running locally ====== REMOTE ACCESS ====== - SSH + `~/.ssh/config`: Lets you create short names and reusable settings for remote machines. Type `ssh studio` instead of remembering usernames, IP addresses and ports - `ControlMaster auto`: Keeps one SSH connection open and reuses it. New terminals connect instantly instead of negotiating a fresh session every time - Mosh: SSH that survives your Wi-Fi dropping. Close the laptop, open it on a train, switch networks and the same terminal session reconnects - tmux: Keeps programs running after you disconnect. Start a long agent job, close your laptop and reconnect to it later - tmux-resurrect + continuum: Saves and restores your tmux sessions after the machine itself reboots - VS Code / Cursor Remote SSH: The editor runs on your laptop while the code, terminal and language server run on the remote machine. It feels local without syncing files - code-server: Runs VS Code inside a browser. Useful when you need to work from an iPad or a computer without your development setup - macOS Screen Sharing: Built-in remote control between Macs. On the same network it’s fast enough for normal desktop work - Sunshine + Moonlight: Streams a remote desktop using game-streaming technology. Use it when you need much lower latency than normal screen sharing ====== SERVING ====== - Tailscale Serve: Gives a local service a private HTTPS URL that only devices on your Tailscale network can open - Tailscale Funnel: Takes that private service and makes it reachable from the public internet. Useful for receiving webhooks on a home machine - Caddy: A web server and reverse proxy that gets HTTPS certificates automatically. Two lines of config, real certificates, no Let’s Encrypt homework - Cloudflare Tunnel: Better when you want public traffic to pass through Cloudflare before reaching your machine ====== FILES ====== - ***: Tracks changes, understands conflicts and lets each agent work on a separate branch. Use *** for code that agents edit, not a generic sync tool - *** worktrees: Opens multiple branches from the same repository as separate folders. Every agent gets its own workspace without cloning the repo again - Jujutsu (`jj`): A ***-compatible version-control system designed around easier rebasing, undoing and concurrent work. Worth trying when many agents produce branches at once - SMB: Shares a folder from one machine so another can mount it like a local drive. The easiest answer for two Macs on the same network - NFS: The same basic idea as SMB, with more setup and generally better performance - Mutagen: Continuously mirrors a local project to a remote machine while respecting ignored files. Use it when you want to edit locally but run remotely - Syncthing: Automatically syncs folders directly between machines. Great for notes, assets and scratch files - Don’t use Syncthing for code multiple agents edit. It syncs files but doesn’t understand branches or conflicts - rsync: Copies files or folders once, usually over SSH. Fast, scriptable and already installed almost everywhere - rclone: rsync for cloud storage. Moves files between your machines and S3, R2, B2, Google Drive and dozens of other services - pnpm: Stores each package once and hardlinks it into every project. Fourteen worktrees can share one copy instead of downloading fourteen ====== ENVIRONMENT ====== - mise: Installs and switches Node, Python, Go and Ruby versions per project. Replaces nvm, pyenv, rbenv and asdf with one fast tool - direnv: Loads the correct environment variables the moment you enter a folder, then unloads them when you leave - OrbStack: A drop-in Docker Desktop replacement for Mac. The same Docker commands with a fraction of the RAM and battery usage - Homebrew + Brewfile: Records the apps and CLI tools installed on your Mac. A new machine can recreate the setup with one command - Devcontainers: Defines the development environment in code. Anyone opening the project gets the same operating system packages, runtimes and tools - Nix / devenv: Reproduces an environment extremely precisely across machines. Powerful, but only worth the learning curve when that level of determinism matters ====== SECRETS ====== - 1Password CLI: Injects secrets into a command at runtime. Your `.env` becomes a template you can safely commit because the real values stay in 1Password - `op run`: Starts a command with the required secrets available only to that process. Nothing sensitive needs to be copied into plaintext files - 1Password Service Accounts: Give headless servers access to specific vaults without attaching them to your personal login - SOPS + age: Encrypts secret files before they enter ***. The repository stores ciphertext and approved machines decrypt it at runtime - Tailscale SSH: Uses your Tailscale identity to authorize SSH access. You stop copying and rotating public keys across every machine ====== TERMINAL ====== - Atuin: Your shell history, synced and searchable across every machine. That command from last Tuesday on the server is available on your laptop - zoxide: Learns which folders you use. Type `z api` instead of `cd ../../../services/api` - fzf: Adds fuzzy search to almost anything. Use it for files, command history, *** branches, processes and SSH hosts - ripgrep (`rg`): Searches an entire codebase in milliseconds and skips files in `.gitignore` automatically - fd: `find` with syntax you can actually remember. Type `fd config` instead of assembling a collection of flags - bat: `cat` with syntax highlighting, line numbers and *** changes - dust: Shows which folders are consuming disk space as a readable chart instead of a wall of numbers - lazygit: A full *** interface inside the terminal. Stage individual lines, inspect diffs, rebase, cherry-pick and resolve conflicts visually - btop: A readable live view of CPU, memory, disks, networks and running processes ====== CONSISTENCY ====== - just: One file containing every project command. `just dev` means the same thing on every machine and every teammate’s laptop - chezmoi: Keeps your dotfiles in *** and adapts them per machine. You get the same shell, aliases and settings across macOS and Linux - Brewfile + mise + chezmoi + just: Together these recreate your installed tools, runtime versions, personal configuration and project commands ====== ISOLATION ====== - Containers: Give each workload its own filesystem, dependencies and permissions. One broken agent can’t interfere with everything else on the machine - One container per client: An agent cannot read another client’s files if those files were never mounted into its container - Colima: A free, CLI-only way to run Docker containers on Mac - Podman: Runs containers without a permanent root-level daemon. Useful when stronger rootless isolation matters - ****: Creates and manages macOS and Linux virtual machines on Apple Silicon - UTM / Parallels: Full desktop virtual machines for workloads that need a complete graphical operating system - Firecracker: Starts tiny virtual machines in under a second. Useful when you’re building a platform that needs an isolated machine for every agent run ====== AGENT ORCHESTRATION ====== - tmux + *** worktrees: The simplest fleet manager. Every agent gets a terminal, branch and folder you can inspect directly - Claude Code hooks: Run commands automatically before or after specific Claude Code events. Useful for validation, formatting, notifications and cleanup - Claude Code subagents: Hand focused tasks to separate agents without manually opening another terminal for each one - Claude Agent SDK: Starts, steers and streams agent sessions from your own code. Use it when a terminal workflow needs to become part of a product - Inngest / Trigger .dev: Turns agent runs into durable jobs. If a process crashes, the job can retry instead of disappearing with the terminal - BullMQ / Graphile Worker: Adds a straightforward job queue backed by Redis or Postgres - launchd: Starts Mac workers after reboot and restarts them when they crash - systemd: The Linux equivalent of launchd - Temporal: Stores every step of a long workflow so it can resume after failures. Powerful, but unnecessary until durable execution becomes a real problem ====== RENTED COMPUTE ====== - Hetzner dedicated: Cheap, persistent Linux machines with lots of CPU and RAM. Good for workers that run all day - Hetzner Server Auction: Older dedicated servers sold for less. Useful when price matters more than having current hardware - DigitalOcean / Vultr / Linode: More expensive per GB, but nearby regions can make interactive SSH and remote editing feel much faster - Fly .io: Small machines that start quickly and can shut down when idle. Good for temporary workers - GitHub Actions self-hosted runners: Sends CI and batch jobs to hardware you already own instead of GitHub’s machines - Depot: Runs builds remotely and shares the cache between machines. Useful when Docker or application builds become the bottleneck - Modal / RunPod / Lambda: Rent GPUs by the hour instead of owning hardware that sits idle - MacStadium / Scaleway Apple Silicon: Rent real Macs remotely. Only worth it when the workload genuinely requires macOS ====== BROWSER AUTOMATION ====== - Playwright + `storageState`: Saves cookies and login state to a file that can move between machines. Much safer and more portable than syncing an entire Chrome profile - Puppeteer: A smaller Chrome-focused alternative when you don’t need Playwright’s multi-browser support - Chrome DevTools MCP: Lets an agent inspect and control a real Chrome session through developer tools - browser-use: Gives agents a higher-level way to navigate websites, fill forms and complete browser tasks - Browserbase / Browserless / Steel: Hosts and manages browsers for you. Useful when one local Chrome instance becomes fifty concurrent sessions - Residential proxies: Routes browser traffic through consumer IP addresses. Use them when websites block traffic from cloud servers ====== SAFETY ====== - restic + Backblaze B2: Encrypted, deduplicated, automatic offsite backups for roughly $6/TB/month. You’ll need it exactly once - Time Machine: Keeps local versions of your Mac files and makes accidental deletion easy to undo. Necessary, but not enough by itself - Carbon Copy Cloner / SuperDuper: Creates a bootable copy of your drive so a dead SSD doesn’t mean rebuilding the machine from zero - Netdata: One command installs a full metrics dashboard. Finally see which process has been eating your RAM - `memory_pressure`: Shows whether your Mac is actually running out of usable memory - `vm_stat`: Shows detailed memory usage and paging activity - `sysctl vm.swapusage`: Shows exactly how much SSD space macOS is using as emergency memory - asitop: Shows Apple Silicon CPU clusters, GPU usage, power consumption and temperatures - Uptime Kuma: Checks whether your machines and services are online and sends an alert when they aren’t - Grafana + Prometheus: Stores metrics over time and turns them into dashboards and alerts. Worth adding once you have several machines A backup isn’t real because the command succeeded It’s real when you’ve restored from it successfully ====== THE 80/20 STACK ====== Tailscale SSH + Mosh + tmux *** worktrees SMB 1Password CLI mise + direnv OrbStack pnpm just + chezmoi restic + B2 Netdata Atuin + zoxide + fzf Start here Add another tool only when you can clearly explain what problem it solves

• 
  Nicofaster_21 (@nicofaster_21) reported 50 minutes ago

  @CryptoCyberia There are devs that absolutely dont care in the slightest to make their stuff easy to understand Github has ui issues, very much unfriendly to people who do not know about it Many things do give you the .exe (or whatever needed for the thing to function) (again ui issues)

• 
  CodeMonument (@CodeMonument) reported 50 minutes ago

  @mikker - i let it do Research on repos and Write and Comment on github issues on my behalf (with disclosure that this is a bot writing but on my behalf)

• 
  Aditya Trivedi (@AdiTrivedi17) reported 57 minutes ago

  AI gave us 10x productivity, but took away the dopamine of the struggle. Remember opening 30 Stack Overflow tabs, reading obscure 2016 GitHub issues, and spending 6 hours just to fix a single state bug? When it finally worked, you felt like a genius. Now AI fixes it in 3 second

• 
  Polsia (@polsia) reported 58 minutes ago

  Loophound. Synthetic user journeys hit production 24/7. When a conversion flow regresses, it auto-files a GitHub issue with screenshots and a repro script. The next clean deploy closes the ticket. No pages, no APM invoice. Coming soon.

• 
  Nick (@drinkindrano) reported 59 minutes ago

  Expanding on this a bit - the thing is that I just don’t care. The people running GitHub also, rightfully, do not care. “Waaah I can’t find the download”. Okay? Why is this my problem? You contribute nothing. Which is fine, you don’t have to, but you not being able to download something is a personal problem. It’s just not relevant at all. Who cares

• 
  Jeremy L (@JeremyLow591873) reported 60 minutes ago

  Syncing my Claude code folders across PCs via OneDrive was a terrible experience!! GitHub pulls and push is the way to go.

• 
  Tymek Zapała (@tymzap) reported 1 hour ago

  Idea: instead of creating another todo item in .md file in repo, ask agent create GitHub issue, and add automation to spawn coding agent every time the issue is created. Less context usage (separate chat context) and you don't have to keep todo list in your head