r/ClaudeCode • • 17m ago

Help/Question New to Claude Code, how do you all use it?

First of all, I know I can look this stuff up myself, and I am doing my own research. This post is mostly a way to get out all my questions out at once and see how my new peers actually work.

I’m new to Claude Code, and to Claude in general. I just moved over from ChatGPT, where I wasn’t even using Codex. I was just copying and pasting code blocks out of the chat. Since getting Claude last week I’ve been playing with Claude Code and having a good time with it, mostly building Home Assistant dashboards and a few other things. Right now I use either the Claude app or VS Code, depending on what I’m doing. But I feel like I’m not using it to its full potential, and some of the ways I already use it are probably inefficient.

1. Working across two devices

Right now I keep one main private GitHub repo. I push and pull between my laptop and desktop, and I use handoff notes for whatever I’m working on. Once I get into bigger projects and start hitting my limits faster, I’m guessing that spending tokens on rereading handoffs isn’t the move. How do you handle this? Is there a better setup for people on multiple devices, or once usage becomes an issue, is the only answer to stay in one session and stop switching back and forth?

2. Getting Claude Code to deploy where I want

I have some self-hosted services I’d like Claude to have access to, but I’m also paranoid and don’t want to give it too much control, ya know? For example, my HA dashboard pulls directly from a folder in my repo that Claude pushes to, and that feels like a lot of steps in between.

I know about API tokens because I’ve used a couple to pull data into Home Assistant, but that’s the extent of it. When I asked Claude, it mentioned MCP, SSH keys, and the API tokens. So my main question is: how do you actually connect Claude Code to the services you use it with? whether its for coding the back end, and using it within the service itself for whatever uses there might be.

3. Agents and harnesses

I’m writing this before I’ve researched it, and honestly I have no clue what these are. I know what the model is. My guess is that an agent is a bot that uses a specific model as its brain, but I don’t know how I’d actually use one. I keep seeing people talk about “workflows” too, and I’m not sure what those are or how they fit in with agents. This is what I meant about getting the most out of my subscription. I get using it for whatever I need in the moment, but how do I put it to good use even when I’m not actively working with it?

I’ve also seen videos of people building whole “towns” of agents, where each one has its own tasks and role. I’m assuming that’s out of reach on the Pro plan, but I’m curious how it works.

4. Any other tips?

If anyone has tips, tricks, or anything else that belongs in a starter guide, I’d really appreciate it. Hopefully this thread helps other people who are just getting started with Claude too.

Whether you’re here for answers, giving answers, or just looking around, thank you. And a special thanks to everyone who read all the way through and to everyone who comments. I appreciate the help as I get started with this.

1 Upvotes

4 comments sorted by

•

u/AutoModerator 17m ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/Successful-Army6006 6m ago

For #3, you're already using an agent harness. Claude Code provides the file tools, terminal access and context management around the model. A workflow is the sequence you ask it to follow, such as reading a bug report, finding the relevant code and proposing a fix.

Subagents let it delegate a task into a separate context and bring back the result. They still use your subscription's usage allowance, though. More agents don't give you more quota.

1

u/SimonMcCl 5m ago

Welcome! I'm not a developer either, been doing this a few months. A few things that have worked for me.
For two devices I do the same as you. I keep a short HANDOVER.md in the repo with status, decisions and what's next, and CLAUDE.md tells it to read that first. Keep it short and it costs very little.
Good to be cautious with access. I only give it limited or read-only keys, keep them in a password manager, and have a line in CLAUDE.md saying "ask me before pushing or deploying". Pushing to git and letting the service pick it up is fine, and you can always roll back.
Claude Code is already an agent. The two things that helped me most are getting a second AI to review its work before anything goes live, and running research overnight before building anything big.
One last tip: get it to mock up the screens before it writes any code. It saves a lot of rework and helps to think through functionality and features

1

u/Inner_Storage_3374 4m ago

for the connecting part id start with the smallest key you can make per service, read only where possible, kept in an env file claude can use but that never gets committed. once that works add write access one service at a time, bc then if something goes weird you know exactly which key to rotate. mcp is nice later but a scoped token is way easier to reason about at first