I suggest putting the tests in a separate folder ;)
AgentsDock: An IDE designed for agentic AI research
21–30 of 41 posts
Re: AgentsDock: An IDE designed for agentic AI research
#22Re: AgentsDock: An IDE designed for agentic AI research
#23It's a 2 day old project. https://github.com/ZhengyiLuo/AgentsDock
Re: AgentsDock: An IDE designed for agentic AI research
#24It's a 2 day old project. https://github.com/ZhengyiLuo/AgentsDock
That is new repo for open source, we've actually worked on it for a while
Re: AgentsDock: An IDE designed for agentic AI research
#25Looks useful! curious how you would compare it against something like Paseo?
Re: AgentsDock: An IDE designed for agentic AI research
#26- arent there 10000 projects that do this - what makes this one special?
Re: AgentsDock: An IDE designed for agentic AI research
#27I went from IDE (VS Code) to terminal (wezterm) running half a dozen agents in an app called Herdr. My computer work is mostly in the terminal now, prompting agents. And they have access to my Obsidian vaults. Can read, and add to them. And access all my notes via a local RAG. I neither need projects in Claude, nor IDEs. Just agents accessing my local vaults and code repos.
Re: AgentsDock: An IDE designed for agentic AI research
#28an ide built around agents instead of files is the direction i keep expecting to win. how do you handle state when several agents touch the same repo at once
Re: AgentsDock: An IDE designed for agentic AI research
#29Earlier quoted context omitted.
Goodness - triggers my ADHD. Power to those who find it useful, I would be so lost in the wrong details (the quota screen is pretty cool).
I sometimes use 5 agents at once, but 3 work on separate tasks and the 4th is watching them by tmux and steering, and the fifth is also watching the whole team for testing quality standards. So 2 out of five are just helping me watch the other 3. But this only works because the 3 worker agents have really separate problems, almost no connections across.
Re: AgentsDock: An IDE designed for agentic AI research
#30an ide built around agents instead of files is the direction i keep expecting to win. how do you handle state when several agents touch the same repo at once
Worktrees or sandboxes. You can tell Claude to put its stuff in a worktree. I can easily develop any amount of features in the same codebase because they all run in their own worktree