Capability

It runs on your machine too

Build, run and fix projects on your own computer, including installing the runtime the project needs.

Node.js Python Java .NET Go PHP and Composer Docker Desktop Windows

In your words

Ask it like this

No syntax to learn. These are real requests, phrased the way people actually phrase them.

›this project will not build on my machine ›what do I need installed to run this ›why does npm install keep failing ›run the project and tell me when it is ready ›the build works for everyone else but not me ›stop whatever is holding port 3000

Capability

What it does here

Everything below is what the agent does today, not a roadmap.

Builds and runs your project locally, streaming the output as it goes
Spots a missing runtime and offers to install the right version (Node, Python, Java, .NET, Go, PHP)
Installs come from the official package manager, with the publisher shown before anything downloads
Installs alongside what you already have where the platform allows it, so existing versions are left alone
Reads your project files to work out what it needs before launching anything

What it looks like

One question, one answer, one fix

The checks on the left of each reply are the reads it did before committing to an answer. That is the difference between a diagnosis and a guess.

Every exchange ends in a verified outcome. It goes back and confirms the result rather than assuming the fix worked.

brynko devOps Agent

this project will not build on my machine

read the project checked installed runtimes compared versions

The project targets Node 18 and the build fails on an engine check. You have Node 22 and nothing else. I can install 18 alongside it without touching your 22, then re-run the build. Shall I?

yes, go ahead

installed Node 18 kept 22 in place re-ran the build

Node 18 is installed and your 22 is untouched, both are on the machine now. I re-ran the build and it compiled. The dev server is running on port 3000.

Build passed · running on :3000

Common cases

The ones that cost you an afternoon

Each of these is a specific failure with a specific set of checks behind it, not a general promise to help.

It works on everyone else's machine

The project builds fine for the team and fails for you, with an error that does not obviously point at a version.

What it does. It reads the project to find the version it actually targets, compares that against what you have installed, and tells you which one is the mismatch.

A new joiner loses two days to setup

The first task of a new developer's week is a scavenger hunt for runtimes, tools and undocumented config.

What it does. It reads the project, works out what is missing, installs the right versions and gets the build green, so the first day produces code rather than a checklist.

The project needs an old runtime

It targets Java 8 or Node 18, you have something newer, and you do not want to uninstall what your other projects depend on.

What it does. Where the platform allows it, the older version is installed alongside the one you have rather than replacing it, so both projects keep working.

npm install fails

A wall of output ending in an error that is about a native module or an engine version rather than your code.

What it does. It reads the actual failure rather than the last line, which is usually a version constraint or a missing build tool, and tells you which.

Port already in use

The app will not start because something is holding the port, and it is not obvious what, especially after a crash.

What it does. It finds what is holding the port and offers to stop it, killing the whole process tree rather than the launcher that spawned it.

It started, then died, and you missed why

The process exits immediately and the error scrolls past before you can read it.

What it does. Output is streamed and kept, so the error is still there afterwards, and it tells you plainly what the app said on the way down.

Start to finish

What happens between the question and the fix

Point it at the project
A folder is enough. It reads the build files, the lockfiles and the version markers to work out how the project is meant to be built.
It checks your machine
What is installed, what version, and what the project actually needs. Reading is free and needs no permission.
It offers to fill the gaps
With the exact package and publisher shown before anything downloads, from the official package manager for your platform.
It builds, with the output live
No silent spinner, and if it fails you get the real error rather than a generic build failure.
It runs and confirms
Then tells you the app is up, or what it said on the way down if it is not.

The part that matters

Reading is free. Changing asks first.

Reads run instantly and need no permission, because reading cannot break anything. Anything that changes a system, whether that is a restart, an edit, an install or a delete, stops and tells you what it is about to change, on which server, and why. You see it written out, as the command it will run or a red and green diff of the file, so you are approving the actual thing rather than a description of it. Changes are backed up first, so undoing one is a click.

Read the security model

Questions

Local Development, specifically

Will it uninstall or upgrade what I already have?

No. Where the platform supports side-by-side versions, it installs alongside what you have and leaves your existing setup alone. Installing Java 8 for one project does not take away the 17 another project needs.

Where do the installs come from?

The official package manager for your platform, and you see the package name and publisher before anything downloads. Nothing is fetched from an arbitrary URL.

Does it need access to my servers to do this?

No. Local work happens entirely on your own machine. Servers are a separate thing you add when you want them, so you can use this side without registering anything.

Can it run my project, not just build it?

Yes, with the output streamed live, and it can stop a runaway process properly by killing the whole process tree rather than the launcher.

Does it work on Windows?

Yes. Windows is the platform the desktop app ships on today, and it understands PowerShell, batch files and Git Bash, so a Windows machine is not a second-class case. macOS builds are available on request.

Does it change my project files?

Only with your approval, shown as a red and green diff first, and the original is snapshotted so reverting is one click.

Also covered

The rest of the stack

A real file editor for your Linux servers, no nano required

Browse your Linux servers as a file tree and edit files in a real editor with syntax highlighting, find and replace and search across the whole box. Over the SSH access you already have, with nothing installed on the server.

Docker, without memorising the flags

Inspect containers, read logs, check stats, restart services and run Compose stacks, just by describing what you want.

Your reverse proxy, explained and fixed

Test configs before they go live, read the right log, and reload safely, on nginx, IIS or Tomcat.

Ship it, and know what shipped

Run your existing deploy scripts, watch the output live, and get a straight answer about whether it worked.

Ask your database what is wrong

Read-only checks and queries over your existing SSH connection, with credentials encrypted at rest.

Wildcard HTTPS, sorted in one step

Issue trusted, auto-renewing certificates, wildcards included, and get the paths handed straight back.

Try it on something that already annoys you

Point it at one server. You will know within an hour whether it earns its place.

Create an account See pricing