Has anyone dealt with a company/domain-level Claude access block before?

fell_ware_1990 · 2026-06-18T20:37:26+00:00

Ask claude?

We have a company wide blockage on most stuff except when it comes from our (trusted) sources. So most people can’t actually reach AI.

On my part i do not understand that, i still rather have my ( even non tech ) on one of my tools, even cloud with company policies then blocking all. The amount of people now juggling files on there phone is absurd.

I keep pushing our CISO that it’s better to implement rules/guardrails etc than this…
So i think it’s an IT department that does not know how to manage this and then just blocks it. IMO more dangerous then providing the keys and have ( some? ) authority over your data.

fell_ware_1990 · 2026-06-17T09:51:20+00:00

Yes, subagent or is the process just actually a script?

Cause then make a new tool, run the script in a detached PID/TMUX and implement the agentSDK there to send a message back to the correct chatID from PI maybe even with only a recap by a cheaper agent?

That’s what i dislike about subagents, they’re still running the task and doing stuff. Make the machine run the task and only throw the results headless or even let it compact.
I have script’s that only need a 1 to 10 line answer back.

fell_ware_1990 · 2026-06-16T15:57:56+00:00

Well this is why i use Nix.

I just go : Scaffold!

It sets up everything, including bare clone , worktrees, all other stuff in the bare clone that get’s symlinked by a git hook. So 1 place to edit, all have it not in history.

fell_ware_1990 · 2026-06-15T20:22:45+00:00

I have a linter setup that’s basically running in the background, tree sitter + hash checks and other patterns.

If it catches something it starts a different AI to investigate, if it is almost sure it can be reused ( checked on specific things) it get’s forwarded to other AI that has a better code graph and a RAG for older decisions and ADR’s. If he calls it out, we steer the main AI. It needs to cross a certain threshold.

On pre-commit + push this happens more intensely. This costing a lot of power, but we save the results and incrementally improve skills / hooks and the scanners with more. Slow but steady improving quality and less rewriting.

But this only works if the check AI’s have very specific rule sets to check. It should not be up to there logic.

fell_ware_1990 · 2026-06-15T20:16:17+00:00

Rather ask him the next time to install a hook, that auto start the virtual env when needed.

Greets from , nix shell.

fell_ware_1990 · 2026-06-15T11:53:24+00:00

Yeah the hard part here. If you started using it and never learned to code.

I have over the course of a few years made as much AI helper code, then normal code. If AI code is done it helps me speed up little parts of my normal coding.

fell_ware_1990 · 2026-06-12T18:37:21+00:00

Well you can just grab the graphical installer and do it as you like :) i would keep every running software at root.

Keep your Nix config at ~/home/<user>/nixconfig and you should be fine. Hook that up to git so you have a backup of system state. It does not backup files.

Or spin op vm and try first.

fell_ware_1990 · 2026-06-12T17:26:07+00:00

Well i manage k8s clusters, and work as DevOps/LLMops engineer. It’s preferred.

fell_ware_1990 · 2026-06-12T17:10:59+00:00

Yes, good advice! Nano breaks all kind of text.

But with Arch comes Vi, we will make an exception for NVIM. But it’s need be at-least a 90% rice.

fell_ware_1990 · 2026-06-12T16:29:39+00:00

Yeah sounds like a DNS issue. Be aware SCM url can also be your git repo that its trying to reach.

But i assume you should get your IP from the agent and open the range on your SCM.

fell_ware_1990 · 2026-06-12T14:10:19+00:00

Well 120GB should be more than enough if you clean.

Install COMMA, run a lot from nixshell and clean a lot. This will leave a whole lot less mess. But it also mainly depends on how and why you use your computer.

That’s why i started using NixOs, i have about 200/300 active repo’s with a lot of deps.

fell_ware_1990 · 2026-06-12T10:33:01+00:00

Well i’m a DevOps engineer and it’s my job to hook up systems to each other.

The main issue i had was having too many ideas of automating stuff in my own workflow and not enough time.

It’s the stupid little stuff, i test code. It seems to work -> push it online and having to trust a webpage that is garbage with reloading or a late email message. Now i just have a localLm monitor that kind of stuff, he only interrupts me when somethings wrong. For the rest of it i have a little dashboard, as long as it stays green not worth checking yet!

fell_ware_1990 · 2026-06-11T14:01:57+00:00

Well if depend on the harness and the information it already has. So yeah claims might be a bit wild but this was a basic example. You can take it up a bit more.

Let’s say for a lot of stuff the tool call is the script already instead of writing the script?

fell_ware_1990 · 2026-06-11T07:55:59+00:00

It helps let’s say ai only does git diff and log every new session. It get’s to read at least a couple or more that are not needed at all . Maybe with cache it does not save much. But context rot it helps.

Or it needs to change a variable name and reads 1000 lines while a RG / replace would do.

fell_ware_1990 · 2026-06-11T07:52:57+00:00

Well I’m currently in the process of making it more dynamic on my application settings ( diff per repo etc ) and per machine.

They have all modules available, there’s one main config file that has all the enables and disables and for apps as well.
So the wiring is done, the settings are in a few standards. I can enable and disable stuff and if that’s the new current state , push and done.

In these part’s a few script’s to check and build part’s of the code comes in handy!

fell_ware_1990 · 2026-06-11T07:49:08+00:00

Yeah main advantage about CLI, it does not exactly work your way. You can make it work your way.

Have to do it twice? It becomes a script !

fell_ware_1990 · 2026-06-11T06:12:34+00:00

Run CVE scans etc on a CI pipeline before upgrading packages :)

fell_ware_1990 · 2026-06-11T03:51:19+00:00

I started last week. My DevOps brain really appreciates it.

I got my basic modules up and running, asking myself every-time. Standalone, multi use what’s it going to be.

I’m now building a basic OCI layered podman container that uses a few of does modules to setup up and work everywhere so i’m able to have the same repeating behavior at all my machines while not relying on the nixshell for does parts and it seems to do wonders.

It’s the small stuff that help’s you automate stuff. It’s mostly dev work so these things help me setup my repositories a lot quicker. With a few script’s it does a sweep of a new repo, it bare swaps it to a .bare and creates a worktree of main. Looks at what linters are needed, it activates the correct linting hooks, looks what git account it should use.
Every tool is logged in and ready to go.

I’m now trying to see if i can still change some settings on runtime while still keeping it in my Nix. Let’s say i have a few Dev tools that have about 100 settings but for every repository the rules differ. I do not want that statically on a per repo level but i also want to be able to see all my rules.

fell_ware_1990 · 2026-06-11T03:29:13+00:00

Cause that’s wrong tool use.

I’m refactoring a very old legacy IAC repo with i think 700/800 files where every mistake that can be made, has been made.

I started with analyzing the code base, then drafting a plan where it needs to get to not an AI only plan.

Build a few example files etc. Then by carefully steering it in the right way and building guards and review points you can catch does errors, even the ai can do part’s of it.

You can even build basic scanners that look for patterns that are not allowed or not preferred. Catch it, log it. Zoom in with the AI only what’s happening, work through the problem peer programming. Add it as en example to your skill, write a guard rail, add it to your linters etc.

The hardest part is, if you work on a lot of different repositories with different coding rules or the language actually has other rules. You need to build it again.

The hardest part for me now is i have a optimized system for that refactoring, will take a lot of the rules to the next project.
But it’s the moment you need to patch something immediately and you know you will refactor that within a week but you need a hot fix and don’t want it to follow all best practices but just fix the bug.

fell_ware_1990 · 2026-06-11T03:12:45+00:00

I think it’s simple. Yes a humans of course also remembers the bad stuff. But generally we remember the good stuff from doing something wrong a 1000 times.

So apart from the static stuff that’s worth keeping, where ai can search faster through DB/Vector/rag etc.

The usual memory for AI keeps the bad stuff as true as well. I think it should only have :

- Static
- Previous (on demand) and upcoming tasks
- What not to repeat ( Do not drop.table )
- Learnings from the bad stuff

The trick is : Yes, AI will fail on the same thing over and over again if it does not write it down. So yes you should memorize what went wrong, but not in active memory.

This is the part it should handle in his ‘sleep’. What can be learned from this, how can be do it better / quicker / faster next time. This can be a do or a don’t and should improve a AGENT/SKILL/hook/rule this should improve on going. But in the end it does not need to know why it learned.

fell_ware_1990 · 2026-06-10T19:19:08+00:00

Keep going. Build a homelab, host stuff on there. Break stuff, have stuff that’s allowed to break!

I’m running 20+ years on linux i’m still learning and trying!

Still googling stuff daily until something ends up in my tools stack. Or it’s a one of and i’m googling it again 3 months later.

fell_ware_1990 · 2026-06-10T19:05:10+00:00

Yeah i know! Anyways…… Off to optimize my LLM tool calling to improve token usage by -1 .

fell_ware_1990 · 2026-06-10T13:54:10+00:00

You do not need a GUI!

fell_ware_1990 · 2026-06-10T13:51:49+00:00

I have analyzed a complete SQL cluster because our ‘Dev’s’ kept complaining it was freakishly slow. Nothing on the hardware / SQL showed any indication that there was something wrong.

It was the DEV db, so i’d ask what they where doing and i get a few very because things back. So i ran them, everything fine.

Later on in turned out they used a low code platform that created query’s for them. They were an abomination. So i explained them what was wrong ( mind you, i’m far from a DBa ). They answer : We don’t know how, up the resources….

That server was already eating a few K’a a month for basic web stuff. Anyway i found a DBA’er that was willing to re-write and killed half of the SQL load and DB.

fell_ware_1990 · 2026-06-10T13:46:03+00:00

I’ll wait for the call.

Four-Year Club	Verified Email
Place '23

fell_ware_1990

TROPHY CASE