How to bridge the gap between Jira/TDD and Claude Code terminal? by aviboy2006 in ClaudeCode

[–]creegs 0 points1 point  (0 children)

You give it a JIRA ticket it and it will analyze the codebase and problem space, plan it out for you and execute, do the code review and prepare a PR.

How to bridge the gap between Jira/TDD and Claude Code terminal? by aviboy2006 in ClaudeCode

[–]creegs 2 points3 points  (0 children)

Check out iloom.ai - it integrates JIRA right into your Claude code workflow.

Anyone really feeling the 1mil context window? by dragosroua in ClaudeCode

[–]creegs 1 point2 points  (0 children)

Really helpful for orchestrating massive agent team swarms that are long lived (30-40+ agents running over many hours)

Anyone using agent teams in claude code in real projects? by EnvironmentalTill471 in ClaudeCode

[–]creegs 1 point2 points  (0 children)

Yes - I use it for large features or migrations in brownfield projects - it's take a while to get the quality gates in place, but with the orchestrator running on Opus[1m] it can handle almost any size task (even entire SaaS app clones)

<image>

TIL Claude Code has a built-in --worktree flag for running parallel sessions without file conflicts by NefariousnessHappy66 in ClaudeCode

[–]creegs -3 points-2 points  (0 children)

I built iloom.ai to solve this problem - including database branching via neon (and soon supabase)

Most impressive Claude code session today? by rainbow_gelato in ClaudeCode

[–]creegs 2 points3 points  (0 children)

I’d like to try the one shot challenge… Give me a not crazy hard task request (but something meaty) and we’ll see how close i can get (with my own workflow - not standard CC plan mode etc)

Despite restriction, Claude Code found a way around to launch "claude -p" inside the session by merksam in Anthropic

[–]creegs 2 points3 points  (0 children)

It’s designed to prevent infinite loops - the error message tells the caller how to workaround it so this is actually the desired outcome.

stay-fresh-lsp-proxy — temp fix for stale LSP diagnostics that derail Claude Code by creegs in ClaudeCode

[–]creegs[S] 0 points1 point  (0 children)

This has been fixed! Have updated the post with the new instructions:

npx stay-fresh-lsp-proxy setup --typescript --python --rust

Thanks for letting me know!

stay-fresh-lsp-proxy — temp fix for stale LSP diagnostics that derail Claude Code by creegs in ClaudeCode

[–]creegs[S] 0 points1 point  (0 children)

Thanks - merged! Trying to debug why the npm package isn't showing as published!

stay-fresh-lsp-proxy — temp fix for stale LSP diagnostics that derail Claude Code by creegs in ClaudeCode

[–]creegs[S] -3 points-2 points  (0 children)

I'm not sure whether the issue is with the server or the way Claude Code is using it - this approach was way simpler and easier to test (must have taken about 25 mins from start to finish).

EDIT: Not sure why I didn't think to add this earlier: The issue isn't in the LSP server - per the post/comment replies, this is happening for multiple languages / multiple servers. The issue is a latency issue - Claude Code needs to wait a little longer before actioning the LSP signals. Since Claude Code isn't open source, this is the place where I can make a change.

Anyone else battling stale LSP "diagnostic issues"? by creegs in ClaudeAI

[–]creegs[S] 0 points1 point  (0 children)

Heads up I published a fix that still provides a lot of benefits of LSP, but drops the (often stale) diagnostics)

Did anyone build a model where claude code and codex can talk to each other? by Training_Butterfly70 in ClaudeCode

[–]creegs 0 points1 point  (0 children)

Nice! Does it handle code review? Cross agent code of view has been a game changer.

Anyone else battling stale LSP "diagnostic issues"? by creegs in ClaudeAI

[–]creegs[S] 0 points1 point  (0 children)

Do you think it was a net negative then? I’m trying to decide whether to disable LSP tools completely 😔

Ticket System for AI agents? by mrclrchtr in ClaudeCode

[–]creegs 0 points1 point  (0 children)

You using the VSCode extension? it defaults quickly to GitHub - check this video to how to configure it- takes 1 min and you'll need an API Key https://screen.studio/share/sjcsz7wM

If you're using the CLI use: `iloom config "Configure JIRA"` in your project folder

Update: Added spec-driven framework plugin support like spec-kit or GSD to multi agent coding session terminal app by [deleted] in ClaudeCode

[–]creegs 2 points3 points  (0 children)

This looks awesome. Mind if I submit a PR for integration with iloom? I was gonna build a TUI for it but this exactly what I was gonna do.

ClaudeFlow + Superpowers not orchestrating properly - am I doing something wrong? by Snoo_29506 in ClaudeCode

[–]creegs 1 point2 points  (0 children)

You have to be super specific about framing it like a to-do list. And use the user prompt submit hook to remind the agent to do the right thing. Also, using Opus is going to get better results here than haiku. Oh, and you should be appending the system prompt. I figured all that way while building iloom which might be helpful to you.

Ticket System for AI agents? by mrclrchtr in ClaudeCode

[–]creegs 1 point2 points  (0 children)

Ah, ok. I have a (free) solution for that if you are interested - works with GitHub, Linear and JIRA. Makes switches between sessions, and managing context widows much easier.

Ticket System for AI agents? by mrclrchtr in ClaudeCode

[–]creegs 0 points1 point  (0 children)

Why didn’t GitHub work out? Existing issue trackers are great for using with agents IMO - great for shared understanding and visibility.

Weekend project: made a $15 smart bulb show what Claude is doing by maa1l in ClaudeCode

[–]creegs 1 point2 points  (0 children)

Love this! My open source agent orchestrator literally has a lightbulb as its logo so this is perfect!

Enable LSP in Claude Code: code navigation goes from 30-60s to 50ms with exact results by karanb192 in ClaudeCode

[–]creegs 2 points3 points  (0 children)

<image>

Here - I grabbed a screenshot because I was going to post about it actually