What do I do first, and who has to do it?

#What you need

• An account. Free, and it does not ask for a card.
• A machine that holds the code. Windows, macOS or Linux. The program that runs there is published for five targets: Windows on x86-64, macOS on Intel and on Apple silicon, and Linux on x86-64 and on ARM64.
• A coding agent on that machine. Claude Code or Codex. The analysis is done by the agent you already use, under its own terms.
• A person at that machine for about five minutes. Your developer, your agency, or you. They run two lines in their own terminal and say one phrase. After that the agent works on its own.

#Create a project

A project is one system: the product, service or set of services you want to understand. Give it the name you use for it. Creating it sets up the place where the knowledge about that system is kept, separate from every other project.

The project page then says what it needs next, which at this point is a machine to analyse it from.

#Connect the machine

The connection page in the cabinet hands the person at the machine two lines, for PowerShell on Windows or for a shell on macOS and Linux. Both are run in their own terminal, by them, not by the coding agent.

1. Install 1adk-agent

   The install line fetches the program from the same address the person is signed in to, checks it against the published checksum and only then installs it. Once per machine. Updating later is the same line again, and the cabinet says when a machine is behind.

   On Windows it goes into a folder under the local application data and onto the PATH. On macOS and Linux it goes into the local bin folder of the user.

2. Connect the project folder

   The connect line carries a pairing code that works once and expires within minutes. It is run in the repository folder and names the coding agent with --for claude or --for codex, so 1adk-agent registers itself as a local tool server for that agent.

   Once per repository. A project has one live connection at a time.

The credential the machine ends up holding is never shown on a page. It is created during the exchange, kept by 1adk-agent on that machine, and can be ended from the cabinet.

#Start the analysis

Open the coding agent in the same folder. If it was already open, restart it, so that it loads the tool server the connect line registered. Then say:

That is the whole instruction. The agent asks 1adk-agent for work, does one small unit at a time and hands each answer back through the same tools. The cabinet shows the analysis moving and whether the machine is connected. The same phrase picks the work up again after any interruption.

#When it finishes

A connected analysis goes into the project by itself once it has been checked. The project page then shows the map of the system, the registry of its interfaces, the evidence under each claim, what is still unknown and how much of the system is established.

The second analysis is where the comparison starts. «Carry on learning» on the project page asks the same connected machine for the next pass, and the person there opens the coding agent and says the phrase again. 1ADK cannot start a coding agent remotely, and does not try to. The free plan covers two accepted analyses of one project, and after that the project stays readable and further analyses wait.

Reading the result goes through each part of the project.

#Who does what