luca-ctx

8 ms·

31.
Why coding agents need a merge queue(ctx.rs)
3 points by luca-ctx 4mo ago|0 comments
32.
by luca-ctx 5mo ago
Congrats Zed! GPUI has been a huge inspiration. Whenever I think to myself “yikes that sounds too hard”, my next thought is “well, Zed team could probably do it”.
33.
by luca-ctx 5mo ago
The plan is for the app itself to remain free, no account, fully local, bring-your-own agents/endpoints/tokens, etc. We will add paid options for Team/Enterprise when we exit our beta which include features for policy enforce
34.
by luca-ctx 6mo ago
Yes, it’s free for individual local use, and you don’t need an account. The upcoming paid plans will be for team/enterprise and managed services: org policy/security controls, shared history/collaboration, and optional hosted
35.
by luca-ctx 6mo ago
Ah I missed that, my mistake. It is fixed now. To confirm, it is not open source.
36.
by luca-ctx 6mo ago
Yes, we allow fully local without github/PR involved. For worktree creation, we support both git and jj.
37.
by luca-ctx 6mo ago
It is for issues reporting, similar to Claude Code.
38.
by luca-ctx 6mo ago
I think your concerns are valid and echo a lot of what I've heard from others experiencing the same uncertainties. --- RE: Sandboxing and Permissions --- First, make sure you know the Lethal Trifecta: https://simonwillison.n
39.
by luca-ctx 6mo ago
Glad it helped!
40.
by luca-ctx 6mo ago
Thank you for flagging, I am fixing now and will update this thread when it's ready.
41.
by luca-ctx 6mo ago
We’ve felt the same thing and tried to make ctx work well in multi-repo setups. There are basically two ways to approach it: - If one repo is primary and the others are mostly reference material, use workspace attachments. That lets the age
42.
by luca-ctx 6mo ago
Definitely agreed. One thing we found works really well is having the agent read the other agent’s plan document when it hits a merge conflict, not just the diff. A lot of conflicts are hard to resolve correctly without the intent behind th
43.
by luca-ctx 6mo ago
It is a rust project, just not source available.
44.
by luca-ctx 6mo ago
You can't avoid merge conflicts from happening, but you can definitely empower the agents to self-resolve them. The workflow is like this: 1. an agent works in its own worktree 2. its changes are green in isolation 3. it submits that w
45.
by luca-ctx 6mo ago
That is our issues-only repo, similar to Claude Code. It is not open source.
46.
by luca-ctx 6mo ago
ctx sits around the agent harness, not in place of it. So Claude Code, Codex, OpenCode, etc keep their normal tools/capabilities rather than being reimplemented inside a new proprietary agent. If a harness has its own indexing/cod
47.
by luca-ctx 6mo ago
I agree. I don’t think most of these products should be forking and maintaining a whole IDE. That’s also not how I think about ctx. The UI is a workbench around agents, not a replacement for IntelliJ/VS Code. If you need deep code navi
48.
by luca-ctx 6mo ago
Yes. The important distinction is that ctx sits above the agent harness, not above the raw model APIs. With something like Cursor, you can use models from OpenAI, Anthropic, etc, but they still run through Cursor’s own agent harness. With c
49.
by luca-ctx 6mo ago
Yes, our view is that the ADE shouldn’t be where you do most code navigation. The ADE is best for steering multiple agents and reviewing their changes, especially once you care about isolated worktrees, diffs, artifacts, and landing changes
50.
by luca-ctx 6mo ago
OP here. Happy to answer questions. The multi-thread, worktree-based interface will probably look familiar. The parts HN may care more about are the containerized workspaces, remote-host model, and local merge queue for multi-agent work.
51.
Show HN: ctx – an Agentic Development Environment (ADE)(ctx.rs)
53 points by luca-ctx 6mo ago|52 comments
52.
by luca-ctx 6mo ago
Author here. One thing I left out of this post was how ACP (agent client protocol) didn’t work for us when building ctx. I’ll be writing more about what we think could be better.
53.
by luca-ctx 7mo ago
Context rot is definitely still a problem but apparently it can be mitigated by doing RL on longer tasks that utilize more context. Recent Dario interview mentions this is part of Anthropic’s roadmap.
54.
by luca-ctx 7mo ago
> I don't let LLMs write text for my blog. Thank you Simon and I'm sure you would quickly fall off from #1 blogger on HN if you did. I insist on this for myself as well. Somehow we are all getting really good at detecting &quot