nowfound

Alternatives

Products that do what BackSpace does

Understand and recover from AI-generated code changes

  1. 1

    Generate, refactor & debug with GPT-4. All inside VSCode

    2023

  2. 2

    Persistent memory for AI coding agents

    Apr 2026

  3. 3
    Codespace254

    A beautiful cross-platform code snippet manager

    2020

  4. 4
    codefy.ai116

    Code faster with powerful AI tools

    2023

  5. 5
    gait168

    Git-Blame for AI-Generated Code

    2024

  6. 6

    The AI coding agent that never compacts

    Feb 2026

  7. 7

    The AI teammate for your editor

    Oct 2025

  8. 8

    Your AI agents team, terminals, notes: one infinite canvas

    Jul 2026

  9. 9
    Repodex118

    Automatically find and fix errors

    2023

  10. 10

    Cursor, Windsurf, Claude, Prompt, Code Generation

    2025

  11. 11
    GPS83

    Memory layer for LLMs that stores repo rules + past lessons

    May 2026

  12. 12
    Horizon134

    Understand AI generated code and integrate packages.

    2025

  13. 13
    Coderrr96

    Open source CLI-first AI coding companion

    Jan 2026

  14. 14

    Open-source runtime for internal team software

    May 2026

  15. 15
    CodeBurn103

    See where your AI coding spend actually goes

    25d ago · codeburn.app

  16. 16
    WarpGrep114

    Remove context rot + improve code search

    Dec 2025

  17. 17
    Stash107

    Gives you context from your codebase, issues, and docs

    2025

  18. 18
    DexCode94

    Your AI Agent builds the Deck & you never leave the terminal

    Mar 2026

  19. 19

    Local semantic search for AI agents

    30d ago · tryreference.com

  20. 20OD

    Hello HN! I built OpenCodeSpace https://github.com/ngramai/opencodespace — a CLI tool that lets you launch disposable, self-hosted VS Code environments in one command. It’s like a self-hosted Code Spaces, but: - Works locally with Docker or remotely on Fly.io (AWS, GCE coming soon) - Auto-configured with Claude Code, OpenAI, Gemini CLI - Designed for YOLO mode development: temporary, parallel, throwaway sessions As Claude Code and Gemini CLI became core to my dev workflow, I kept needing a way to run them in parallel, in clean, isolated environments in full YOLO mode…

    2025

  21. 21NO

    We're open sourcing Nimbalyst, a multi-agent, visual workspace for building with Claude Code, Codex, and Opencode (alpha). It pairs parallel session management with WYSIWYG editors so you and your agents can work on the same files at the same time. The core idea: agents edit files, you edit files, and Nimbalyst makes that collaboration legible. Built-in WYSIWYG editors cover markdown, mockups, Excalidraw diagrams, data models, spreadsheets, and code (Monaco). Every edit is tracked back to the session that made it, with red/green WYSIWYG markdown diffs for review and approval. A session…

    Apr 2026 · github.com

  22. 22CA

    I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!

    Sep 2025 · infrastructureas.ai

  23. 23WA

    Today you can easily adopt AI coding tools because you have git for branching and rolling back if AI writes bad code. We haven't seen this same capability for data and decided to build it ourselves. Nile is a new kind of data lake, purpose built for using with AI. It can act as your data engineer or data analyst creating new tables and rolling back bad changes in seconds. We support real versions for data, schema, and ETL. We'd love your feedback on any part of what we are building - https://getnile.ai/ What do you think?

    Jan 2026

  24. 24HP

    Hi HN! I'm building Hopsule. If you use AI coding tools like Cursor, Copilot, or Claude, you’ve probably seen this happen: The AI writes good code - but it ignores your architecture. It doesn’t know: - why you chose a specific pattern - which conventions your team agreed on - which decisions are already locked in So it falls back to generic patterns, outdated examples, or random GitHub training data. Over time this slowly breaks the consistency of the codebase. Most teams try to fix this with: - giant Markdown files - wiki pages - long prompts - Slack threads But those aren't…

    Mar 2026

Ranked by how close each launch is in meaning, then by votes. Refine with a description →