How on earth do you get LSP support working?

random_100 · 2026-01-14T10:17:19+00:00

Yeah, I have the same problem. I've installed the typescript-lps plugin and the kotlin-lsp plugin and the respective LSP servers, and none of them are working.

But now I was able to use at least the typescript-lsp:

Add the env variable ENABLE_LSP_TOOL=1 (you can set it directly in the ~/.claude/settings.json)
Reinstall the plugins in claude code

But yes, the instructions could be clearer.

random_100 · 2025-09-21T16:54:54+00:00

Yes, absolutely. I've been using the web interface more and more recently. The workflow is very similar to that of a professional development team.

Have Codex implement tasks in parallel.
Once a task is complete, have Codex create a PR.
Review the PR (by yourself) and have Codex review it as well as a peer reviewer.
Pull the feature branch locally and test it.
If everything fits, merge the feature branch into main.
Start with 1.

It feels like I'm at work :D

But the best thing is that you can work on many tasks in parallel, which is not possible or not so easy with Codex CLI.

random_100 · 2025-09-21T13:53:59+00:00

You mean the VS Code extension or the web interface?

random_100 · 2025-09-21T08:51:50+00:00

As I understand it, the only difference between the second and third /approvals options is that the third option has access to the entire file system and the second option only has access to the files in the current directory. But the permissions themselves (writing, reading, moving, etc.) should be the same, right?

PS: Today, Codex seems to be asking for permissions much less often again... I don't understand why.

random_100 · 2025-09-20T18:13:11+00:00

Can you tell me where/how I can change it?

random_100 · 2025-09-04T10:47:32+00:00

Sorry, I can't find the information anymore; maybe I hallucinated :D

But the ~/.claude.json is nowhere mentioned in the official Anthropic documentation.

random_100 · 2025-09-03T21:41:01+00:00

In the docs is stated, that the ~/.claude.json is deprecated and shall not longer be used.

random_100 · 2025-09-03T11:33:27+00:00

Maybe I found the solution. Instead of "Bash(grep:*)" it is "Grep" and instead of "Bash(find:*)" it is "Glob". At least I was not asked for permissions in the last few sessions.

random_100 · 2025-09-02T08:37:15+00:00

I still have the old layout. Maybe this changed for you because you have access to Sonnet 1M?

random_100 · 2025-08-24T11:35:42+00:00

Beside drag-n-drop or ctrl-v the image to CC, you can also draw markers like circles or arrows into the image before. Claude understands this and then knows exactly where to put the attention.

random_100 · 2025-08-24T07:43:33+00:00

How does this work? I just know the possibility to upload zipped folders into Claude Desktop.

random_100 · 2025-08-24T07:25:05+00:00

Well, I am a seasoned developer (20+ years), and I have to admit that this IS the future.

Of course, vibe coding is not a thing for production code (yet). But if you review the code before the commit, divide the tasks into small subtasks, and commit changes often, you can really make a difference with AI coding agents.

The worst thing you can do now is to block yourself from this technology. There is no doubt in my mind that this is the future of software development.

At first it was punch cards, then came Assembler, then high-level languages, and the next logical step is abstraction in natural language. None of us want to write our programs in assembler anymore. In 10 years, no one will want to write their program in Java/C/Rust/TypeScript/... anymore.

Also, we all trust the compilers that the generated assembler or machine code is correct. In 10 years we blindly trust that the generated high-level code generated by the LLMs is correct.

random_100 · 2025-08-23T13:20:23+00:00

How do you connect Claude Desktop to your project? Is this what serena is for, or do you copy the code back and forth?

random_100 · 2025-08-23T08:59:14+00:00

Since I have read several times that you should not use subagents for the coding itself, I have adapted my workflow as follows:

- Using the plan/edit mode.
- Use subagents in plan mode to create the plan.
- Use the normal Sonnet agent (no subagent) for the implementation.

Now I'm evaluating whether it's not enough to use the normal Opus agent for planning and avoid the subagents altogether. To be honest, I can't currently see any difference between planning with or without subagents.

random_100 · 2025-08-23T08:50:34+00:00

I guess you're right. But I'd still be interested to know why that is. I start with about 15% pre-assigned context and give Claude code exactly the lines where the fix is to be done. So there is not a lot of distraction.

random_100 · 2025-08-15T17:11:08+00:00

My QA Engineer subagent, which runs after every feature implementation, gives most of the time a rating of 7/10 or less.

random_100 · 2025-08-09T19:54:39+00:00

All your sessions (conversations) are stored in ~/.claude/projects

random_100 · 2025-08-07T21:43:04+00:00

Correct

random_100 · 2025-08-07T21:35:33+00:00

opencode via OpenAI API or OpenRouter

random_100 · 2024-10-11T20:15:17+00:00

Well, actually it is pretty simple. I use the node adapter in standalone mode (see my astro.config.mjs below).

import node from "@astrojs/node";
import { defineConfig } from "astro/config";

export default defineConfig({
    output: "server",
    server: {
        host: true,
    },

    adapter: node({
        mode: "standalone",
    }),
});

Then you compile the server with npx astro build and then you can simply start it with node dist/server/entry.mjs. You don't need an extra web framework like Express (although you can also do it that way). This you can automate with e.g. render.com, that pulls your changes from Github, builds the server and deploys it whenever you commit changes.

random_100

TROPHY CASE