Andare Code Get in touch

What is planned

Where Andare Code stands today, the work that is scheduled next, and the things it is deliberately not going to do.

Where it stands

The daemon picks up tracker work, runs a coding agent against it and hands back a branch.

What is planned is about how much it may do without being asked, and about running the agent somewhere other than your own machine.

Planned work

What is being built

Grouped by theme and ordered by intent. These are horizons, not dates — nothing on this page is a delivery commitment, and the order can change when a customer gives us a reason to change it.

  • Next

    How much it does on its own

    The useful range runs from "ask me before every step" to "close the ticket and open the pull request". Which end you want depends on the repository and on how well-specified the work is, so it becomes a policy rather than a default.

    • An autonomy policy, configurable per project
    • Clear boundaries on what the daemon may do unattended
  • Later

    Agents in containers

    Running an agent directly on a developer machine is the fastest thing to build and the least appealing thing to operate. Launch adapters let the same work run in a container instead, with the agent of your choice.

    • Container launch adapters for Codex and Claude Code
    • The same tracker workflow regardless of where the agent runs
  • Next

    Getting it and keeping it current

    A desktop daemon needs an install path and an update path before it can be used by anyone who did not build it.

    • Packaged builds, with updates and a release channel
    • Downloading the daemon directly from the Andare interface

Out of scope

Not on the roadmap

Said plainly, because the alternative is a sales conversation that ends in disappointment. If one of these is the thing you need, Andare Code is not the product for it.

  • Writing the specification for you

    Andare Code closes work that is already well described. Deciding what should be built is the part it deliberately leaves to a person.

  • Reviewing its own output

    It hands back a branch for a human to review. Rev-Local is the product that reviews code.

How this is maintained

Every item above corresponds to work tracked in our own issue tracker, and this page is rewritten from that tracker rather than kept by hand. What is not shown: unfixed defects and security work, which belong in the tracker until they are closed, not on a product page.

Want the detail behind a line on this page, or a view of where something sits? Write to dmoore@dwmmholdings.com and ask.

Next

Put Andare Code in your pipeline

Ask about integrating it with the repositories and agents you already run.

This is a pre-production site. All content is subject to finalisation, and nothing stated here is binding until the site is live.