Import an existing app
Already have a codebase? You do not have to start from scratch. Connect CodeSpring to your project and your agent maps it into a mind map you can keep improving with confidence.
Why import
Once an app grows past a few features, it gets hard to hold the whole thing in your head, and that is when an agent starts making changes that ripple in ways you did not expect. Importing gives you the same visual map you would build from scratch, but drawn from the code you already have.
Open your project
Open the app you already have in your editor, and open your coding agent in that same folder. This works with Claude Code, Cursor, Codex, Gemini CLI and more, so use whichever one you already build with. Everything below runs inside that project.
Connect the CLI
Four commands connect this project to CodeSpring. Run them in your terminal, in order.
First, install the CodeSpring CLI. You only need to do this once.
npm i -g @codespring-app/cliLog in so the CLI can reach your CodeSpring account.
codespring auth loginAdd the CodeSpring skill to your agent so it knows how to read and update your map. It works with Claude Code, Cursor, Codex, Gemini CLI, Roo Code and 30+ other tools.
npx skills add CodeSpringApp/codespring-skillsFinally, link this project. Run it inside your project directory so CodeSpring maps the right codebase.
codespring initOr do it in one prompt
Prefer to let your agent handle it? Paste this into Claude Code and it runs all four commands, then reads your codebase and draws it into CodeSpring as features and sub-features.
Set this project up with CodeSpring, then map it out for me. 1. If the CodeSpring CLI is not already installed, install it globally: npm i -g @codespring-app/cli 2. Authenticate by running codespring auth login, and wait for me to finish signing in. 3. Add the CodeSpring skill to yourself: npx skills add CodeSpringApp/codespring-skills 4. Link this project to CodeSpring by running codespring init in the current directory. 5. Then use the CodeSpring skill to read the whole codebase and visualise it in my CodeSpring project. Create the central project node, a feature for each main part of the app, and sub-features for the screens and flows inside them, so the map matches how the code is actually organised. Explain what you are doing at each step, and stop to ask me whenever something needs a decision.
What happens next
Your codebase appears in CodeSpring as a map: a project node at the root, a feature for each main part of the app, and sub-features for the screens and flows inside them. From there you can point the agent at one feature and change it without quietly breaking another.
New to the canvas? The mind map explains what each node is and how the pieces connect, so the map your agent just drew makes sense at a glance.