linsys

Not yet published to npm — npx confessor won't work for others until the user runs npm publish. This gates the launch. <- When do you plan to do this? I was able to run it myself using the directions in the CLAUDE.md but shouldn't they be in thee README.md until it's published?

I'm surprised by this actually but OpenClaw is trash anyway.

My bad. Won't happen again.

It's synced hourly, it uses the API from the 3rd party to determine what has changed and then ingests the changes, it's also how it cleans up the stale data.

For embeddings I am using Titan Text Embeddings V2

I built it to solve my own challenges with my consulting work and sales work. I kept building the same platform over and over to write my book, handle emails with customers, and sales reps, etc.. so I decided to make it a SaaS platform.

I use it personally every day to read my emails, generate drafts because RetriveIT has all the marketing material I have stored in gdrive and github. Sometimes I even use it for silly thigs like I'll ask it "what is my ITIN and what date did I register my company" because I hate having to search though gdrive to find that info when I need it.

It's technically different because unlike claude or chatgpt OAuth is bound at the workspace level not at the user level. A user can be a member of multiple workspaces, and users can share their workspace with other workspaces inside of an orginization.

There is a free signup on the site with email, it uses magic link.

Some of these hidden slash commands are interesting. Good resource you put together here!

But isn't that what Linux admins said when Cloud and Platform Engineering became a "thing".

Puppet, Chef, Ansible they are taking the fun out of system administration, Cloud it's going to take away my job. But what happened is roles changed, SRE, Platform Engineering, dare I say DevOps engineers (whatever those are) all emerged.

Software engineering is going through he same transformation with the same knee jerk reactions from both sides of the argument. Either AI run rampant with no guardrails like OpenClaw people burning 1000s in tokens, OpenClaw calling them randomly at 2am, etc.. then on the other side of the argument we have a petition asking the Node.js Technical Steering Committee to ban AI-assisted code from Node.js core.

AI is here, it's here to stay, I believe that those of us that will be successful will find the middle ground.

If it uses the SDK then it's token burn? Or can it "legally" use your Claude.ai MAX account, your subscription account?

This post was inspired by Alex Tatiyants' 2012 classic "DevOps is Ruining My Craft". Fourteen years later, a new crisis demands the same treatment.

It is an excerpt from an interview with a disenfranchised Python developer. All identities have been kept anonymous to protect the innocent.

This is what we do for our own internal apps, what we do is actually much more complex we ingest all the docs from Github and Confluence AND we generate code-maps into a RAG then we expose it with an MCP, integrate that MCP into claude code so claude can ask for both our coding standards, IaC standards, testing standards, etc.. but also has the full context about the applications it needs to consume from or deliver to.

Did you try using s3 vector?

LOL how is this not DEAD?

Yes, I've run Claude Code using ollama running on my GPU server with a 5090.

Why because 7% of people complain the loudest? I would imagine that most power users have big followings on X, Reddit, HN, etc.. but that hardly reflects the reality of what most people are experiencing.

This is a problem for me when I gain weight, I have a simple snore app on Android and when I was severely overweight it was reporting how many times a night I stopped breathing as I lost weight it happened less and less.

I think the main issue is power users, as long as power users are subsidized by enough paid subscribers then they won't go away. People are paying for subscriptions but not using them 24/7, that's why they want to push power users to non-peak hours like nights and weekends when the platform is more idle.

Personally, I rather see them force Max x5 and x20 users into non-peak meaning cap our usage more during peak hours and give us more tokens to burn in non-peak IF it keeps them from cutting off our paid subscriptions.

I thought we won already.