A-Shell is a powerful terminal emulator for iOS that brings Unix commands to your iPhone or iPad.
It lets you run tools like vim, python, ping, and more right on your device. To make A-Shell work the way you like, it supports configuration files similar to Linux shells.
In A-Shell, your home directory is effectively ~/Documents, so you keep config files there.
For example, you can create a text file ~/Documents/.profile (or .bashrc) and put shell settings or aliases in it.
As Nicolas Holzschuch explains, “all your files, including configuration files (.bashrc, .profile, .ssh…) are in ~/Documents”.
Writing a friendly .profile helps you customize A-Shell’s behavior and save time on repetitive tasks.
A-Shell Configuration Files
When a new A-Shell window (session) starts, the app automatically runs your shell startup files.
By default A-Shell uses dash as its shell, but it still reads certain configuration scripts.
In particular, ~/Documents/.profileand ~/Documents/.bashrcare loaded on each new window. This means you can define environment variables, aliases or custom prompts in those files.
For example, to make a quick directory with md you might add:
- alias md=’mkdir’ (placed in ~/Documents/.profile).
Whenever you open A-Shell or launch a new window, that alias will be ready to use.
Note that because A-Shell treats ~/Documents as $HOME, these config files live there – there is no write-access to the real root home on iOS.
Also, dash (the shell for scripts) reads ~/.profile on startup, but not ~/.bashrc.
Use .bashrc for interactive prompt settings and .profile for things you always want set.
Editing Your A-Shell Config
You can create or edit these files using A-Shell’s built‑in editors.
For example:
$ pico ~/.profile
This opens the A‑Shell text editor on your device. Add any commands you like; common uses are setting $PATH, creating aliases, or defining your prompt ($PS1).
For instance:-
Setting the prompt: Add a line like export PS1=”\u@\h:\W\$ ” to include username and folder in your prompt.
Environment variables: export EDITOR=vim ensures vim is your default editor.
Aliases: As above, alias ll=’ls -la’.
Every time A-Shell starts a new session, it reads these scripts.
The official changelog even notes Every new session loads the .profilefile, for custom environment variables.
To apply changes immediately, simply close and reopen the A-Shell window or run source ~/.profile in the shell.
Customizing A-Shell Appearance
A-Shell also has a special config command to tweak the look of the terminal. You can run config in A-Shell to open an interactive menu, changing the font, color scheme, cursor style, and toolbar buttons.
For example, config -p will make your current window’s settings permanent for future sessions.
These settings are saved internally (not in your .profile), but they show how A-Shell separates appearance from shell behavior.
Best Practices & Tips
Back up your settings. Since your config files live in ~/Documents, consider copying them (e.g. with cp .bashrc ~/config_backup_bashrc) so you can restore if needed.
Test changes carefully. A bad command in .profile could make the shell behave oddly. If A-Shell won’t start normally, you can edit the files via the Files app on iOS or remove them.
Use simple syntax. A-Shell’s default shell is POSIX sh (dash), not full Bash. Avoid Bash-only features or complex scripts without checking them.
Keep prompts basic. Color and special characters can be added with ANSI codes, but overly fancy prompts sometimes break on refresh. Keep it straightforward unless you need the flair.
Learn as you go. You can always echo text or commands in your .profile to check they run. The command echo “Config loaded” at the end of your .profile can confirm it’s working when you start A-Shell.
By tailoring these startup files, your A-Shell experience becomes more personal.
You get a “people-first” terminal setup that meets your needs: quick commands, useful shortcuts, and a familiar prompt.