Stories

I am building a collaborative coding agent

Article news.ycombinator.com

I am building a collaborative coding agent

Hello folks,

I know there are way too many coding agents out there but I believe I am taking a different approach. I am building nocodo for entire teams, particularly for non-technical teams. It is self-hosted and I want to share how I am building it. Happy to hear thoughts and criticisms. At a high level:

  - Runs on a Linux box on your cloud
  - nocodo has a "manager" which is the agent and it runs on Ubuntu Linux
  - Linux makes it easy to setup a full development environment on the cloud so team members do not have to
  - LLMs are OK with multiple languages and frameworks for software development and nocodo does not add any restrictions of its own - no system prompt even at this point
  - nocodo (the manager) is also a headless coding agent, regular HTTP API
  - nocodo does/will (depending on the feature) support managing a Linux box, managing multiple projects, users and teams, permissions, multiple models, coding plans (like GLM 4.6 from zAI)
  - mix and match models for analytical or coding needs, will be mostly done for you
  - Commands, like "build/run [backend, frontend]", "create test DB", etc.
  - Git, GitHub integration, branch/worktree management all through the manager's HTTP API
  - Desktop and mobile (coming) apps for team members to connect to "manager" (let's call them admin apps)
  - Admin apps use SSH and port forwarding to connect to the coding agent
  - Admin apps does/will allow project and prompt management, prompting, collaboration (@ mention team mates into prompts)
  - Admin apps does/will have buttons for the "commands" described earlier, e.g., run the full-stack generated apps, open frontend in browser
I want to add a prompt library, a real-time project context that models can use as a tool to help anyone to improve the technical details of prompts. Or to assist models figure out technical details on their own. Project management, Git management, infra management will also be available as tools to the models. Think `apt install []`. When someone needs full isolation, spinning up another cloud instance should also be possible.

I still have to figure out a bunch of things. I am now showing demos with early prototype. I plan to share a proper "Show HN" in a couple weeks time. I am really focused on non-technical teams and nocodo will have a much heavy server side to get users there. I believe project management will also change as we embrace code generation with LLMs. When features take a couple hours of wrestling with agents instead of days with developers, what will project management look like.

nocodo is itself mostly Rust and that is because I do not want to spend time wrestling with the compiler, but the model can and does it cheap. And the compiler does not allow many types of errors that other languages might. I may nudge nocodo's users, who are backend tech stack agnostic, to also use Go/Rust.

nocodo is itself generated by Claude Code and opencode (using Grok Code Fast 1 and GLM 4.6). I have Claude Pro and a Coding Plan from zAI. Overall about $ 35 / month for about 3 months now.

Personal: I am Sumit. I have been a trying founder and engineer all my adult life. I have been in at least 12 startups across the world. I own nocodo.com since 2013 when I wanted to build a "no code" product. Tried multiple times with ideas around template based code generation. Finally, with LLMs, I can see this may work out at scale. I believe businesses want custom software and they will build (vs buy), if custom software keeps pace with their needs. I live in a little Himalayan village and I have been building LLM enabled products for some time now. nocodo is the one getting real user demand. I have 2 early adopters (founders). I am setting up for 2 small sized businesses now. There is a lot of manual hand-holding I do for them, including jumping into Claude to fix issues nocodo cannot. Please feel free to share your thoughts.

https://github.com/brainless/nocodo

Cheers! Sumit

Discussion 0 comments · 2 points · brainless · 2025-11-24
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    New collection

    Delete this collection?

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Privacy policy · Terms of use

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.