Claude Code - MarekBykowski/readme GitHub Wiki
Claude App for Windows
Claude Code's built-in remote SSH feature -> The SSH remote is about where Claude Code runs — it SSHs into your machine and runs the claude process there directly, so all file operations and commands execute on the remote server.
Refined howto
Install
curl -fsSL https://claude.ai/install.sh -o install.sh
chmod +x install.sh
./install.sh
Then you need to authenticate. Easy, just follow.
Create dir ~/claude-enum and switch to. Then start the claude from within
claude --name claude-enum
Produce remote-control from inside the session
/remote-control claude-enum
After restart or machine reboot
claude --resume
It will launch a session picker.
Get a new session retaining history from the current one.
Create a dir ~/claude-remote-rootport
From within your current session, run
/branch remote-rootport
/cd ~/claude-remote-rootport
exit
History is retained. Go to each parent and forked off claude and run
claude --resume
Claude remote-control
Wersja 1
Jeśli chcesz pracować zdalnie z telefonu/przeglądarki:
cd ~/.claude/projects/-home-mbykowsx-host-repos-cxl_relay
claude rc --name cxl-relay-dev
# potem otwierasz claude.ai/code w przeglądarce
~/.claude/projects/
└── -home-mbykowsx-host-repos-cxl_relay/ ← odpowiada /home/mbykowsx/host-repos/cxl_relay
├── CLAUDE.md ← instrukcje/kontekst dla Claude
├── sessions/ ← historia sesji (--resume używa tych plików)
└── ...
Wersja 2 bardziej ogólna
Authenticate (one-time)
claude auth login # choose claude.ai, NOT API key
Start Remote Control
Server mode (multiple clients, recommended):
claude remote-control --name "My Project"
Single interactive session:
claude --remote-control "My Project"
From inside an existing session:
/remote-control My Project
The terminal displays a session URL and QR code (press spacebar to toggle).
Connect from Windows / any client
- Open claude.ai/code in a browser -> find the session by name (green dot = online)
- Or paste the session URL directly in the browser
- Or scan the QR code from the Claude mobile app
Key options for server mode
| Flag | Effect |
|---|---|
| --name "X" | Custom session title |
| --spawn worktree | Each client gets its own git worktree (isolated) |
| --spawn same-dir | All clients share the same directory (default) |
| --capacity N | Max concurrent sessions (default 32) |
| --sandbox | Enable filesystem isolation |
Resume claude/remote-controle session
Yes, Marek, that's exactly right! Here's the flow:
- Restart tmux:
tmux new -s mb (or reattach if it survived: tmux attach -t mb)
- Navigate to your project directory:
cd /path/to/your/project
- Resume your session:
claude --resume my-project or claude --continue or claude --resume (for the picker)
You don't need to start a fresh claude and then run /remote-control again.
The --resume flag picks up your saved session—including the conversation history—and automatically restarts Remote Control with the same name.
Alternatively, you can use claude --resume without a name to open the session picker and choose interactively.
Get new session retaining history from the before
In your current session, run
/branch new-session-name
to create the fork with shared history. Then immediately run
/cd /path/to/new/directory
to move that forked session to a different directory.
Exit from the original session and
claude --resume
Then switch to the directory of the new seesion and also run
claude --resume
Claude Code CLI
Prerequisites
- Ubuntu 20.04 or later
- A paid Anthropic account (Claude Pro, Max, Teams, Enterprise, or Console with API credits)
curlinstalled- Browser access (via VNC or desktop) for first-time authentication
Installation
- Run the native installer
curl -fsSL https://claude.ai/install.sh -o install.sh
cat install.sh # inspect first
bash install.sh
No Node.js or other dependencies required. The binary is installed to
~/.local/binand auto-updates are configured automatically.
- Verify the installation
claude --version
claude doctor
claude doctor checks your auth status, PATH, and configuration. Run it after every install to catch issues early.
Authentication
- Since you have a browser available via VNC, simply run:
claude
Claude Code will open the browser automatically for you to authorize. The token is saved locally — you won't need to repeat this unless it expires.
Recommended Setup for Yocto Builds
- Install tmux
Long Yocto builds must survive SSH disconnections. Use tmux:
sudo apt install tmux
tmux new -s yocto
Run claude inside the tmux session. If you disconnect, reattach with:
tmux attach -t yocto
- Initialize Claude Code in your project
Navigate to your Yocto project root and initialize:
cd ~/yocto/poky # adjust to your project root
claude
/init
This creates a CLAUDE.md file that gives Claude persistent memory about your project structure across sessions.
Tips for Yocto Workflows
- Point Claude Code directly at log files rather than pasting output:
claude "look at tmp/work/.../temp/log.do_compile and tell me what's wrong" - Use multiple tmux panes — one for
bitbake, one forclaude - Add a
.claudeignorefile to skip large irrelevant directories (e.g.tmp/,downloads/):tmp/ downloads/ *.log
Further Reading
- Claude Code official docs
- Anthropic Console — manage API keys and billing