Skip to content

[Feature]: Support for native shell environment #14

Closed
Closed
[Feature]: Support for native shell environment#14
Labels
enhancementNew feature or request

Description

@rishitank
rishitank
opened on Oct 1, 2025

What would you like to be added?

For some reason, Auggie CLI is set to use the bash shell by default, which causes a whole host of problems, and I am having to tell it to wrap all commands in zsh -ic and ensure to source ~/.zshrc, but even then Auggie forgets these instructions eventually and I have to mention it again. As a side effect of failing to remember to do this, whenever it tries to do a git commit that triggers pre-commit hooks, it fails and as a result Auggie solves this by employing the dangerous solution of either prefixing with HUSKY=0 or using the --no-verify flag. This then causes downstream issues during our CI workflow because operations like linting and type-checking are not followed. Our team all use Mac OS so the default shell is zsh. It would be greatly appreciated if Auggie CLI had native support for the shell it is running on.

Why is this needed?

To avoid broken commands, AI hallucinations and wrong solutions to obvious problems. Auggie thinks that node or npm / pnpm is not installed, which is definitely not the case, and as a result goes down the wrong rabbit hole of trying to fix it...

Possible solution or alternatives

No response

Additional context

No response

Activity

  1. rishitank
    added
    enhancementNew feature or request
    on Oct 1, 2025

  2. binarypie commented on Oct 28, 2025

    @binarypie
    binarypie
    on Oct 28, 2025

    I have this problem even with bash because it doesn't read the local bash profile. I'm constantly telling Auggie to read my user's .bashrc file. It's really really annoying. Claude and Gemini do not have this issue at all.

  3. justinxu421 commented on Oct 28, 2025

    @justinxu421
    justinxu421
    on Oct 28, 2025
    Contributor

    I have this problem even with bash because it doesn't read the local bash profile. I'm constantly telling Auggie to read my user's .bashrc file. It's really really annoying. Claude and Gemini do not have this issue at all.

    Sorry about that, we're working on this, looking into configuration of shells and startup script for the terminal tool

  4. binarypie commented on Nov 3, 2025

    @binarypie
    binarypie
    on Nov 3, 2025

    I have this problem even with bash because it doesn't read the local bash profile. I'm constantly telling Auggie to read my user's .bashrc file. It's really really annoying. Claude and Gemini do not have this issue at all.

    Sorry about that, we're working on this, looking into configuration of shells and startup script for the terminal tool

    FWIW you can probably look through the Gemini cli source code to see how they do it. I was actually surprised that Auggie's CLI isn't available. This would have been an easy community contribution.

  5. binarypie commented on Nov 4, 2025

    @binarypie
    binarypie
    on Nov 4, 2025

    I have this problem even with bash because it doesn't read the local bash profile. I'm constantly telling Auggie to read my user's .bashrc file. It's really really annoying. Claude and Gemini do not have this issue at all.

    Sorry about that, we're working on this, looking into configuration of shells and startup script for the terminal tool

    FWIW you can probably look through the Gemini cli source code to see how they do it. I was actually surprised that Auggie's CLI isn't available. This would have been an easy community contribution.

    If your .bashrc guards against non-interactive shells like many default configuration do. I have a workaround for anyone who is waiting for this feature. This is bash specific but probably translate to other shells.

    1. Look for the guard at the top of your .bashrc file it'll look something like this:
    case $- in
*i*) ;;
*) return ;;
esac
    1. Next move all of your environment variables and path modifications above this line.

  6. justinxu421 commented on Nov 24, 2025

    @justinxu421
    justinxu421
    on Nov 24, 2025
    Contributor

    should be configurable and fixed in latest release

  7. justinxu421
    closed this as completedon Nov 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions