Skip to content

Feature: show nicer message after project creation #202

Open

Description

@kfirstri

I see many errors "No Base44 project found. Run this command from a project directory with a config.jsonc file." meaning users run their CLI from outside of a base44 dir,

  1. we need to somehow make sure this is actually the case and not that we have a bug
  2. can we direct the user once create command end to do "cd ./create folder", just incase they don't know / they agents doesn't know

@claude please add the message on create command to also do cd into their folder

Activity

  1. self-assigned this
    on Feb 8, 2026
  2. added theissue type on Feb 8, 2026
  3. claude commented on Feb 8, 2026

    @claude
    Contributor

    Claude finished @kfirstri's task in 1m 48s —— View job • claude/issue-202-20260208-1101 • Create PR ➔


    Completed

    Tasks

    • Read CLAUDE.md for project guidelines
    • Locate the create command implementation
    • Review current completion messages
    • Add cd instruction to the outro message
    • Commit and push changes
    • Provide PR creation link

    Summary

    I've successfully updated the base44 create command to display a helpful cd instruction after project creation. This addresses the issue where users were encountering "No Base44 project found" errors by making it clear they need to change into the project directory.

    Changes Made

    Modified src/cli/commands/project/create.ts to:

    • Detect when a project is created in a directory other than the current one (i.e., not . or ./)
    • Add a clear "Next step" instruction with the cd command in the outro message

    Before:

    Your project is set up and ready to use
    

    After (when project is created in a subdirectory):

    Your project is set up and ready to use
    
    Next step: cd ./my-project
    

    This provides clear guidance to both human users and AI agents about what to do next, reducing confusion and preventing the "No Base44 project found" errors.

    Note about Build/Lint

    I wasn't able to run bun run build or bun run lint as these commands require approval in the GitHub Actions environment. The code change is straightforward and follows the existing patterns in the codebase, using the theme utilities for styling as per the CLAUDE.md guidelines.

  4. added a commit that references this issue on Feb 8, 2026
    0ea2043
  5. moved this from Backlog to In progress in CLI Developmenton Feb 8, 2026
  6. moved this from In progress to Ready in CLI Developmenton Feb 10, 2026
  7. moved this from Ready to Backlog in CLI Developmenton Feb 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions