A small part, with a gain at every start: no more cd ~/kingo-pod && ... before Claude Code.
11. Start Claude Code with one short command
So far, you went into ~/kingo-pod before each start of Claude Code. After this step, two letters start it, from any
folder: kc.
Your turn.
New here? What is different for you in 4 and 5
In 4, kingo status needs n8n and Langflow. Paste this line in its place: it shows the version of your kingo-pod.
kingo version
Skip 5: kc alone starts Claude Code for the course.
-
Go into your kingo-pod folder. Paste this line into your terminal:
cd ~/kingo-pod -
Let kingo add the short commands:
./kingo shortcutskingo shows a list of five and asks: “Which ones?” Type
1 5and press Enter: that iskcandkingo. kingo says where it wrote them, and: “They work in every new terminal.” -
Open a new terminal tab (how). There, go to your home folder, away from kingo-pod:
cd -
Try the first short command there. It shows the state of your kingo-pod:
kingo status -
Start Claude Code for the course, as
./kingo claudedoes:kcType
/exit. -
Start Claude Code in the folder of your website:
kc ~/projects/my-first-projectType
/exit. -
Are you in the right folder already? Then a dot is enough: it stands for the folder that you are in. Go into the folder of your website, and start Claude Code there:
cd ~/projects/my-first-projectkc .
Why a dot? And why the dot in ./kingo?
In the terminal, a dot means “here”: the folder that you are in. So kc . starts Claude Code here. Two dots mean the
folder above: cd .. goes one folder up.
./kingo claude reads the same way. ./kingo is the file kingo here, in the folder that you are in: that is why you
went into ~/kingo-pod first. Without ./, i.e. if you type just kingo, the terminal would not look for it here:
it looks up the name in its address book, a list of where its programs are. The word claude in ./kingo claude tells
kingo what to do: start Claude Code.
Now that you ran ./kingo shortcuts, the short command kingo needs no ./ and works from any folder:
kingo wrote into this address book where it lives. Likewise for kc.
Keep in mind: without the dot, kc starts Claude Code for the course, wherever you are. kc alone is the same as
kc ~/kingo-pod.
Done: from now on, kc is all you type to start Claude Code, from any folder.
The five short commands. The number is the one in kingo’s list.
| Number | Short command | What it does |
|---|---|---|
| 1 | kc | Alone: Claude Code for the course, as ./kingo claude. kc .: in the folder that you are in. kc ~/projects/my-first-project: in that folder |
| 2 | kcl | the same as kc, with --login: your Claude subscription pays (step 1) |
| 3 | ky | the same as kc, but Claude Code does not ask for your OK before it runs a command or changes a file. The sandbox still decides where it may write (step 9). Use it only when you watch (step 6) |
| 4 | kyl | the same as ky, with --login |
| 5 | kingo | ./kingo from any folder, for example kingo status or kingo update |
Want more of them later? Run ./kingo shortcuts again, and type all the numbers that you want, also the ones that
you have: for example 1 2 5. A number that you leave out, kingo takes out.
Where does kingo write the short commands?
Into the file that every new terminal reads at its start: on a Mac ~/.zshrc, in Ubuntu ~/.bashrc. Its name starts
with a dot, so ls does not show it. kingo writes the short commands between two marked lines and changes nothing
else in the file. First, it keeps a copy of the file, next to it: for example ~/.bashrc.kingo-backup-20261118-130500.
With kc and kingo, the lines look like this (here for Anna on Ubuntu):
# >>> kingo shortcuts >>>
# Made by ./kingo shortcuts, which replaces these lines when it runs again. To take them out: '/home/anna/kingo-pod/kingo' shortcuts remove
if [ -z "${KINGO_SHORTCUTS_SKIP:-}" ]; then
unalias kc kingo 2>/dev/null
function kc { '/home/anna/kingo-pod/kingo' kc "$@"; }
function kingo { '/home/anna/kingo-pod/kingo' "$@"; }
fi
# <<< kingo shortcuts <<<
Each short command calls the file kingo in your kingo-pod folder. So when you update kingo-pod, the short commands
get the update too. To see your lines, paste on a Mac:
grep -A 10 ">>> kingo shortcuts" ~/.zshrc
In Ubuntu:
grep -A 10 ">>> kingo shortcuts" ~/.bashrc
To change them, run ./kingo shortcuts again; do not edit the lines yourself. On Windows, Notepad would even break
the file: Ubuntu could not read it any more.
To take them out again: ./kingo shortcuts remove, in your kingo-pod folder.
From kingo-pod: ./kingo shortcuts help.
Your habits on one page
| Habit | What it gives you | Where it comes from |
|---|---|---|
| Know the model inside Claude Code | You know whose mistake it is, what it costs, and how to change it | How Claude Code works |
| Write the facts of your setup into its start file (in kingo-pod, kingo does it for you) | Claude Code guesses less | Tell Claude what it can’t see |
| Plan first when you are not sure what you want | You see a wrong idea in the plan, not in the work | Brainstorm with Claude first |
| Say what “done” looks like, and ask for proof | Claude Code can check its work against your goal | Give Claude a check to run |
| Tell Claude Code what it cannot see | Less guessing, less cost | Write a specific prompt |
| Watch, and press Esc when it goes in circles | You lose minutes, not an hour | Steer the session |
/clear after two failed tries and for a new task | Better answers, lower cost | Steer the session |
| Work on a copy where there is no undo | You try ideas without fear | How Claude Code works; here: Langflow and n8n |
| Know where Claude Code may work, and give each project a folder of its own | The course stays clean, your project too | kingo-pod: the sandbox and its keys; Permissions |
Want more? Optional · More room for Claude Code →
If something goes wrong
Find your step.
Step 11
| What you see | What to do |
|---|---|
New here: No container engine found, after kingo status or kingo update | These commands are for n8n and Langflow, which you do not need. kingo version shows which kingo-pod you have. To update kingo-pod, paste cd ~/kingo-pod && git pull. |
command not found, after kc | You are still in the old tab: open a new terminal tab. Still not? Paste cd ~/kingo-pod, then ./kingo shortcuts, and type 1 5 again. |
kingo says that kc already means something in your terminal | Another program uses that name. Type yes to take kingo’s kc in its place, or press Enter to keep yours, and start with ./kingo claude as before. |