frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Ask HN: Tips for transitioning from web development to embedded/firmware?

45•llmblockchain•3d ago•32 comments

Ask HN: I have been unemployed for 2y. 15 years of experience, US. What to do?

711•LetThingsBeDiff•1d ago•810 comments

I'm Peter Roberts, immigration attorney who does work for YC and startups. AMA

131•proberts•2d ago•176 comments

Ask HN: Where the company's employees launch the tools that Claude created

3•vmuhammadsaid20•7h ago•2 comments

Ask HN: Is Anthropic being public better or worse for your org?

7•ares623•11h ago•5 comments

Ask HN: Are the trades a safe career transition?

29•Rd6n6•2h ago•43 comments

Tell HN: OpenRouter prompts to Minimax may have been read

61•dannyw•1d ago•11 comments

Does anybody read their emails anymore?

6•ky0ung•1d ago•18 comments

Ask HN: Any actual balanced reviews of GTA 6?

12•tetris11•2d ago•21 comments

Ask HN: What's stopping us from putting agents in general purpose robots?

12•ex-aws-dude•1d ago•7 comments

GitLab 19.6.0 is out and still vulnerable to Ruby2Shell and NGINX2Root

28•hoechst•3d ago•8 comments

Ask HN: Should Uber Ratings Decay over Time?

12•AB3TZ•1d ago•5 comments

Ask HN: Rust, Zig, or C?

9•selectedambient•1d ago•25 comments

Ask HN: Where do you see Software in 5 years?

24•Odbyteusz•2d ago•34 comments

Ask HN: Why no AI-led memory vulns in Python?

11•uticus•2d ago•2 comments

Open-Source FPGA The "startup idea" to "go big fast"

2•daly•17h ago•12 comments

Ask HN: When does your app need its own UI vs. using it via MCP?

13•amoorthy•3d ago•12 comments

The End of Continuous Rework

5•alexhr•2d ago•2 comments

Ask HN: Do you feel developers are more "grumpy" these days?

7•ksajadi•1d ago•11 comments

Interesting Learnings Working for a Startup

21•Jessiejia11•4d ago•9 comments

Second Brain and Agent Maintenance Thoughts on AI Usage?

5•harrisonsmith10•1d ago•1 comments

Ask HN: Cheapest CPU Vms

14•mrkn1•3d ago•10 comments

Anthropic should give stock to Stack Overflow (and OpenAI too)

13•thetjmccarty•2d ago•6 comments

Ask HN: What is your current hardware set up?

5•dfdydx•1d ago•7 comments

Claude Gets Hella Paranoid

19•noduerme•4d ago•14 comments

Ask HN: Did books that went viral on HN publish their manuscript?

4•illidan1000•2d ago•5 comments

Ask HN: How do you manage the curse of rabbit hole?

11•BOOSTERHIDROGEN•3d ago•7 comments

Ask HN: What still makes you proud?

2•logicallee•2d ago•12 comments

Tell HN: /tmp is hogging your RAM on Ubuntu 26

10•boldi•3d ago•4 comments

You've reached the end!

Open in hackernews

Ask HN: Where the company's employees launch the tools that Claude created

3•vmuhammadsaid20•7h ago
Hi everyone,

Here is a situation: In a typical company these days, many employees are creating tools using AI (Claude & Cursor) to help with their work. They run these tools on their own computers, which no one else can use or on a builder platform with a public URL and either no login or a hand-rolled one the agent wrote.

Question: Where do they run this? Who can see it? What happens if an employee leaves the company?

Comments

giacomoforte•2h ago
Good question. The answer is that software is now personal and disposable. If the employee leaves and you do not have access to their personal software utilities you just vibecode your own instead, and you'd actually prefer to do this anyway since you can style your software as you please.
codingdave•1h ago
> They run these tools on their own computers...

Where are you seeing this? Because I'm not.

I'm seeing them integrate AI into existing tools. I'm seeing companies deliver internal AI platforms where people can set up their own tools and processes. I'm seeing internal IT and dev shops build internal tools using AI. But I have not seen a single person vibe-code software that they install and run on their local system. Quite the contrary, the access control on local systems does not even allow installs of non-approved software.

michaelfleicher•1m ago
Treat them like any other internal app, not like a personal file. Run them on company infrastructure behind the SSO you already have, never on a public URL with a homemade login. Every tool gets a named owner, and there is one shared list of what exists and what data each tool touches. Offboarding should include the question "which of your tools do other people depend on". Once a tool touches client data and more than a couple of people rely on it, it is not a script anymore and needs the same review as anything else you ship.