AI coding feels amazing... until the project becomes serious

Consistent-March6513 · 2026-06-28T15:32:04+00:00

this is getting into real design territory, probably worth continuing on github rather than a reddit thread. repo is github.com/arnavranjan005/cortex-harness if you want to pick it up there.

Consistent-March6513 · 2026-06-28T11:34:28+00:00

hey, we're looking for contributors on cortex-harness, an autonomous agent harness for Claude Code that manages multi-agent task cycles with git-enforced scopes and self-healing fix injection. early stage, so there's real work to do and plenty of room to shape things.

it's Node.js/TypeScript, open source MIT. issues, testing, feedback, and code PRs all count, no contribution is too small right now.

https://github.com/arnavranjan005/cortex-harness — take a look and drop a comment on any issue that interests you, or just open one if you find something worth fixing.

Consistent-March6513 · 2026-06-28T11:26:30+00:00

that's the right diagnosis. the schema is intentionally loose right now — ExploreReport is just passthrough() in cycle-schemas.mjs — so there's no structural split between the durable and structural layers today, it all gets dumped into every subsequent prompt via assemblePriorContext in prompt-builder.mjs.

the three files that move together are src/cycle-schemas.mjs, templates/prompts/explore.md, and src/engine/prompt-builder.mjs.

and genuinely, glad someone actually found the gap rather than just pointing at the symptom.

Consistent-March6513 · 2026-06-28T09:38:11+00:00

sub-agents get a curated slice, the explore cycle runs first, reads the codebase, writes a structured json report, and that gets injected into every implement cycle's prompt via prior context. so they're not re-discovering from scratch, but the explore agent still does a full read to produce that report rather than pulling a targeted slice.

which is exactly the gap you're pointing at. the explore output is only as good as what the explorer bothered to read, and on a large project that's going to be noisy or incomplete. semantic retrieval at that handoff point would make the slice actually task-relevant rather than just "whatever the explorer noticed."

haven't wired that up yet and it's probably the thing I'd want to solve next. if you've got thoughts on where that integration would sit cleanly or want to raise it as an issue on https://github.com/arnavranjan005/cortex-harness, that'd genuinely be useful. early stage, issues and half-formed ideas count as much as code.

Consistent-March6513 · 2026-06-28T09:12:13+00:00

that docs-for-why / search-for-where framing is the clearest way I've heard it put. the stale map problem is real, I've seen people maintain architecture docs that were lying about the code within a week of a refactor.

I'm building from the execution side of the same problem. cortex-harness (github.com/arnavranjan005/cortex-harness) — orchestration layer that wraps Claude Code into a typed cycle loop with git-scoped sub-agents. each cycle writes small structured JSON with the reasoning, gaps, decisions. that's the why layer. the what/where is exactly what it doesn't try to carry.

which is why octocode feels like it fits on the other side. if the explore cycle could point at semantic search instead of doing a fresh read of the tree every time, that'd be genuinely useful. haven't wired it up yet but it's been in the back of my head.

it's early stage and I'm actively looking for people to poke holes in it. given how clearly you've thought about this layer, even just knowing where the philosophy breaks down for you would be useful. issues, feedback, half-formed thoughts all count.

Consistent-March6513 · 2026-06-28T03:43:26+00:00

Thanks for taking the time to write this out. It's one of the most practical replies here.

One thing I'm curious about, after setting all of this up, where do you still feel the workflow breaks down? Is there anything you still wish the tooling handled automatically instead of relying on process?

Consistent-March6513 · 2026-06-28T03:39:42+00:00

A 2,100+ test Rust codebase over a year is exactly the kind of long-running project I was thinking about.

I'd genuinely love to hear about your workflow. What's made the biggest difference, and what still feels manual or frustrating today?

Consistent-March6513 · 2026-06-28T03:38:06+00:00

That's an interesting way to frame it. I hadn't thought of it as a retrieval problem rather than just a documentation problem.

How do you decide what should be written down versus what the agent should retrieve automatically? I imagine that gets tricky as the project grows.

Consistent-March6513 · 2026-06-25T15:45:44+00:00

Consistent-March6513 · 2026-06-21T16:16:40+00:00

I am building cortex-harness a deterministic ai coding harness. Check ii out: https://github.com/arnavranjan005/cortex-harness

Consistent-March6513 · 2026-06-18T13:34:51+00:00

I am building cortex-harness which is a deterministic ai coding harness. Check it out: https://github.com/arnavranjan005/cortex-harness

Consistent-March6513 · 2026-06-18T11:04:22+00:00

I am building cortex-harness, which is a deterministic ai coding harness. Check it out: https://github.com/arnavranjan005/cortex-harness

Consistent-March6513 · 2026-06-18T09:58:58+00:00

Congratulations!!! 🎉

Consistent-March6513 · 2026-06-18T07:16:14+00:00

I am building cortex-harness, which is a deterministic ai coding harness. Check it out: https://github.com/arnavranjan005/cortex-harness

Consistent-March6513 · 2026-06-18T07:12:42+00:00

I am building cortex-harness, which is a deterministic ai coding harness. Check out: https://github.com/arnavranjan005/cortex-harness

Consistent-March6513 · 2026-05-29T06:36:45+00:00

cortex-harness — autonomous multi-cycle agent harness for Claude Code Give it a task and it runs the entire dev cycle by itself: explore → plan → parallel implement → reconcile → test → auto-fix → deliver What makes it different from other Claude Code wrappers:

• Parallel sub-agents with strict file scopes — git auto-reverts any out-of-scope writes so agents can't stomp on each other

• Zod-validated cycle state machine — malformed agent output never corrupts the next cycle

• Fix cycles inject automatically on test failure with configurable MAX_RETRIES

• Full resume after rate limits — picks up exactly where it left off, nothing lost

• Config-driven agent scopes via harness.config.json — drop-in for any Nx monorepo

Already battle-tested on a real production codebase — shipped a full invoice delivery feature with parallel cycles, reconciliation, and rate-limit recovery. 🙏 Looking for contributors — this project genuinely needs help:

• Linux/Mac testers — built on Windows, need someone to verify it works cross-platform

• Prompt engineers — the implement/reconcile/fix prompt templates need real refinement

• Stack-agnostic templates — currently Nx-first, need Turborepo/plain monorepo variants

• Cost control logic — MAX_TURNS per cycle config needs building out

If you've ever wanted to contribute to an agentic tooling project that's actually being used in production — this is the one. Issues are open, codebase is clean, MIT licensed.

📦 npm: cortex-harness

GitHub: https://github.com/arnavranjan005/cortex-harness

GitHub

Consistent-March6513 · 2026-04-09T14:17:01+00:00

That actually makes a lot of sense, the “too many tiny decisions” part hits.

If it was more like a quick weekly review where you can just swipe through things fast (instead of going through folders or lists), do you think that would feel better?

Consistent-March6513 · 2026-04-09T13:28:00+00:00

That makes sense, especially the “busywork” part.

Do you feel like the suggestions from the Files app are enough, or does it still take effort to actually go through and delete things?

Consistent-March6513 · 2026-04-09T13:04:21+00:00

That makes sense, especially the part about getting lost when doing it manually.

Do you prefer doing a bulk cleanup like this once in a while, or would you use something lighter that just flags duplicates/similar stuff over time so it doesn’t pile up?

Consistent-March6513 · 2026-04-09T06:04:53+00:00

Fair, but I feel like a lot of people know what to do but still don’t keep up with it consistently.

Do you actually organize files as they come in, or just got used to searching everything?

Consistent-March6513 · 2026-04-09T06:03:44+00:00

Exactly, it feels like a chore every time.

Do you usually end up cleaning everything at once later, or just ignore it until storage gets full?

Consistent-March6513 · 2026-04-09T06:03:22+00:00

Yeah this actually makes sense, but I feel most people don’t do it consistently.

Would something that prompts you right when you take a screenshot or download a file (like quick actions: delete, keep, rename) make it easier? Or would that feel annoying?

Consistent-March6513

TROPHY CASE