▲ 1 r/amodei

Where do you draw the line with auto-approving terminal commands for Claude / coding agents?

Lately I’ve been using MCP servers and AI agents more in my everyday dev workflow—mostly for things like running test suites, checking git status, or inspecting project structures. It definitely speeds things up, but I still get paranoid about giving an agent full permission to run terminal commands freely.

Right now, my general approach is:

- Auto-approve: Read-only stuff (checking files, running tests, checking logs).

- Manual check: Installing dependencies, database migrations, or anything touching git push / environment variables.

For anyone using Claude or coding agents on daily projects—do you just manually approve every action, or have you set up sandboxed environments (like dev containers or Docker) so you can just let it run without babysitting every step?

Curious how others are balancing speed vs. safety here.

reddit.com
u/himfirst_130603 — 18 hours ago

What I learned building my first custom MCP server for local database queries (and why standard API wrappers aren't enough)

I recently started hooking up Claude Desktop to my local development environment using the Model Context Protocol (MCP), specifically to let Claude query a local SQLite database during development without having to constantly export CSVs or copy-paste schema definitions.

Here are a few quick takeaways and design patterns that made the setup much smoother:

  1. Define Explicit Resource Schemas

Instead of just giving Claude a raw query execution tool, exposing a dedicated get_table_schema resource upfront cut down tool-use errors significantly. Claude can inspect tables first before trying to construct SQL statements.

  1. Restrict Mutating Tools

If you're testing custom tools with local data, separate your tool definitions into read-only (e.g., execute_select) and mutating (e.g., execute_update). For local dev, requiring manual approval in Claude Desktop for mutating actions prevents accidental row drops or overwrites during experimental prompts.

  1. Error Handling Matters More Than Output

When an SQL query fails inside an MCP tool handler, return the exact database driver error string rather than a generic "Query failed". Claude is surprisingly good at self-correcting typos in column names or syntax errors if the stderr/error payload is verbose.

// Example snippet from claude_desktop_config.json

{

"mcpServers": {

"local-db-inspector": {

"command": "node",

"args": ["/path/to/my-mcp-server/build/index.js"],

"env": {

"DB_PATH": "./dev.sqlite"

}

}

}

}

Are you guys mostly using pre-built community MCP servers (like Postgres or GitHub) or writing custom servers for specific local workflow automation? Curious what patterns have worked best for your setups!

reddit.com
u/himfirst_130603 — 3 days ago

​[FOR HIRE] UGC Creator for Tech, Gaming, and Everyday Gadgets (Casual Unboxings & First Impressions)

Hey everyone, I’m building out my portfolio for user-generated content and looking to work with brands in the tech, mobile accessory, and gaming space.

I focus on clean, authentic videos that look like genuine recommendations rather than overly polished ads—great for TikTok, Instagram Reels, or YouTube Shorts.

What I can make:

Unboxing & initial setup videos

Quick product reviews / feature highlights

Voiceover commentary or simple text-on-screen demos

Details:

  1. Turnaround: 3–4 days after receiving the product

  2. Rates: Starting around $40–$50 per video (flexible depending on video length and script requirements)

  3. Portfolio: DM me and I’ll send over my recent sample clips and drive folder.

If you’re a brand or seller looking for straightforward video content, drop a comment or send me a DM!

reddit.com
u/himfirst_130603 — 3 days ago

The biggest gap I see in PE / Buy-Side associate candidates isn't modeling—it's commercial intuition. How do you actually train it?

When preparing for buy-side recruiting (specifically LBO modeling tests and technical interviews), most candidates spend 90% of their time grinding financial models, LBO mechanics, and edge-case accounting questions.

While you obviously need a clean, error-free model to pass the initial screen, the candidates who actually get the offer usually stand out in the second half of the case presentation: the strategic and commercial discussion.

A clean model proves you can do the analyst work, but the deal team wants to know if you can think like an investor. A few subtle things that seem to separate top candidates:

  1. Focusing on downside protection first: Juniors often get caught up in pitch-book style expansion cases. Partners want to know what happens if revenue drops 15%, churn spikes, or customer concentration hits a wall.

  2. Understanding unit economics over headline revenue: Being able to break down CAC payback, gross margin sustainability, and pricing power matters way more than just extrapolating top-line growth.

  3. Asking the right diligence questions: Instead of just accepting management forecasts, asking “What specific operational lever has to go right for this margin expansion to happen?” shows real commercial awareness.

For those who have made the transition to PE, HF, or VC—what was the biggest mindset shift for you moving from sell-side execution/modeling to buy-side evaluation? Any specific habits or resources that helped build that investor lens earlier in your career?

reddit.com
u/himfirst_130603 — 3 days ago

I make $120 a month renting out a single 2000s iPod Video to film students and music video directors

A few months back, I was cleaning out my closet and found my old, beat-up 5th-gen iPod Video sitting in a box of cable clutter. It still booted up, so I was originally just going to list it on eBay for like twenty bucks.

Before doing that, a friend who shoots music videos for local bands mentioned how hard it is to source authentic tech props from the mid-2000s without paying ridiculous collector prices online. On a whim, I posted a listing on a local gear-share site and Facebook Marketplace offering to rent it out for $30 a day for prop use on indie sets, photo shoots, or vintage aesthetic music videos.

To my total surprise, it gets booked 3 or 4 times a month. Film students, nostalgia photographers, and indie directors pick it up, use it for a afternoon shoot, and bring it right back. It costs basically nothing to maintain, takes up zero space, and turned a piece of e-waste sitting in my closet into a steady trickle of pocket money.

Anyone else have weirdly specific old electronics or everyday items that ended up accidentally earning money as props?

u/himfirst_130603 — 3 days ago

How Model Context Protocol (MCP) Transforms Local Workflows + Quick Setup Notes

Hey everyone,

If you've been experimenting with Claude Desktop recently, you’ve likely seen how Model Context Protocol (MCP) changes the game for connecting LLMs to external data sources and local tools seamlessly.

Instead of writing custom API wrappers for every single service, MCP provides an open standard to let Claude interact directly with local databases, filesystems, Git repositories, and web services.

Key Concepts at a Glance

MCP Hosts: Applications like Claude Desktop that initiate connections

MCP Clients: Maintain 1:1 connections with servers within the host app.

MCP Servers: Lightweight programs that expose specific capabilities (e.g., PostgreSQL query access, GitHub APIs, local filesystem tools) via standardized protocol messages.

Sample Desktop Configuration (claude_desktop_config.json)

Here is a quick example of how simple it is to register local MCP servers in your configuration file:

{

"mcpServers": {

"filesystem": {

"command": "npx",

"args": [

"-y",

"@modelcontextprotocol/server-filesystem",

"/Users/username/Desktop",

"/Users/username/Projects"

]

},

"github": {

"command": "npx",

"args": [

"-y",

"@modelcontextprotocol/server-github"

],

"env": {

"GITHUB_PERSONAL_ACCESS_TOKEN": "your_token_here"

}

}

}

}

u/himfirst_130603 — 4 days ago

Simple outreach tweak: Stop sending "hire me" pitches and start

Hey everyone! Wanted to share a quick strategy shift that helped me go from getting ghosted on 90% of my cold emails to consistently locking in brands for monthly UGC content.

Early on, my outreach looked like every other creator’s: a dry DM or email saying "Hey! I love your products, I’m a UGC creator and I’d love to make content for you!"

Needless to say, it didn’t work. Brands get dozens of those every day.

What Changed: The "Value-First" Audit Pitch

Instead of asking for work right away, I started spending 5 minutes reviewing a brand’s TikTok or Instagram Reels before reaching out.

Here is the exact framework I use now:

Find a gap in their existing content: (e.g., a missing hook, poor lighting, or a top-performing ad format they haven’t tried yet).

Send a 60-second Loom or quick breakdown: Show them why a tweaked hook or dynamic UGC angle would improve their click-through rate.

Offer 1 high-converting concept for free: "If you want, I can script out 2 quick hooks for your current bestseller—no charge."

Free Tools & Resources I Use for Outreach & Research

If you need good places to find brand inspiration, analyze ads, or format your portfolio cleanly, here are a few tools I rely on:

Inspiration & Ad Audits: Meta Ad Library – Look up brands to see what ad concepts they're actively running and where UGC could plug in.

Portfolio & Pitch Deck: Canva UGC Templates – Keep your portfolio clean and simple; prioritize case studies/results over pretty aesthetic pictures.

Cold Email Outreach: Hunter.io – Great for finding direct contacts for marketing managers instead of emailing info@brand.com.

Key Takeaway

Brands don't want to hire a creator just to shoot video—they want to hire someone who understands conversion. When you show them you actually watched their content and understand their target customer, the conversation flips from "What are your rates?" to "When can we start?"

For those pitching right now: Are you relying mostly on cold DMs, email outreach, or inbound platforms (like JoinBrands/Bazaarvoice)? What’s had the highest response rate for you lately?

reddit.com
u/himfirst_130603 — 4 days ago

We hit the scaling wall. The meta in 2026 isn't bigger LLMs—it’s "AI Runtime Layers" and Self-Verification.

For the past few years, the playbook for better AI was simple: throw more compute, more tokens, and more parameters at the problem. But we’ve officially hit the wall with traditional pre-training scaling laws (like Chinchilla). The high-quality public data pools are drying up, and training tokens are hitting diminishing returns.

Because of this, the entire AI infrastructure landscape has quietly shifted over the last few months from massive model scaling to advanced post-training and runtime execution architecture.

If you are building tools or applications right now, these are the real shifts worth paying attention to:

  1. The Rise of the "AI Runtime Layer"

We are moving past simple API wrappers (Input → Prompt → Response). Instead, the industry is standardizing a new infrastructure category: the AI Runtime Layer. Think of it like an operating system built specifically for LLMs that dynamically handles:

Persistent memory & context management

Live KV cache compression (like Google’s recent TurboQuant research to manage long-context memory overhead)

Dynamic tool routing and model switching on the fly .

  1. Moving from Human-in-the-Loop to Self-Verification

The biggest bottleneck with multi-step AI agents has always been compound error rates—if step 2 fails by 5%, step 5 is completely off the rails.

The current breakthrough driving production-grade agents right now is autonomous self-verification. Instead of relying on a human to approve every step, architectures are integrating internal feedback loops and "auto-judging" layers. The agent evaluates its own output against constraints before moving to the next node in the graph, making long-term, multi-hop workflows actually viable for production.

  1. Open-Weights "Cognitive Density"

Because massive frontier models are incredibly expensive to run for basic tasks, there is a massive push toward cognitive density—packing extreme reasoning capability into smaller, highly specialized models.

With open-source gaps closing rapidly and frameworks like the Model Context Protocol (MCP) standardizing how models talk to local databases and development environments, the center of gravity is moving back to independent developers building hyper-efficient, localized agent loops.

What are your thoughts? For those building production apps, are you spending more time optimizing your agentic graphs and runtime layers, or are you still relying heavily on prompt engineering the biggest proprietary models?

u/himfirst_130603 — 5 days ago

Spent the last few months doing UGC on SideShift. Here’s what actually surprised me.

Hey everyone,

I’ve been quietly grinding away on SideShift as a UGC creator for a bit now, and since I see a lot of people wondering how the platform actually operates under the hood, I figured I’d share my honest experience so far.

How it actually works

If you're new, the workflow is pretty straightforward. You browse the available campaigns, look at the briefs to see if they fit your style, and apply. Once you’re locked into a campaign, you create the content based on their guidelines and submit it directly through the dashboard.

So far, I've worked on a mix of tech reviews and casual lifestyle app demos.

What surprised me the most

Honestly? The speed of the approval process. On a lot of other freelance networks, you end up ghosted by brands for weeks. Here, the communication has been surprisingly tight, and the platform layout makes it easy to track exactly where your submission is sitting.

Lessons learned & a few tips for beginners

If you are just getting started, here are a few things I wish someone told me on day one:

Don't over-complicate the brief: Brands know what they want. Stick closely to the hooks and key pointers they give you instead of trying to reinvent the wheel.

Lighting is everything: You don't need a high-end DSLR camera. Just filming near a bright window makes a massive difference in whether a video gets accepted or sent back for revisions.

Watch your deadlines: The platform keeps tight track of timelines, so only take on what you can actually finish on time.

Overall, it’s been a solid, reliable stream of side income for me. It takes some consistency, but the learning curve isn't steep at all.

Let me know if you guys have any questions about setting up your profile or dealing with briefs—happy to help out in the comments!

reddit.com
u/himfirst_130603 — 6 days ago

From curious newbie to getting results on SideShift

I started on SideShift a few months ago with zero expectations—just curious if UGC was something I could really do. Fast forward to now, I've worked on a few campaigns and learned so much along the way.

Here's what surprised me the most:

Brands actually give you creative freedom.

Clear briefs make creating content much easier (and more fun).

The community is really helpful, especially if you're just starting out.

Some lessons I've learned: Read the brief twice (seriously). Be yourself—authentic content performs better. Don't be afraid to ask questions if something isn't clear.

One of my videos even got used in paid ads, and that was such a rewarding moment. It reminded me that even if you're just starting, your content can still make an impact.

If you're new to SideShift, my advice is to stay consistent and keep creating. Your first few posts might not be perfect, but every campaign helps you improve.

Happy to answer any questions about my experience. Just leave them in the comments!

reddit.com
u/himfirst_130603 — 7 days ago