GuidelinesFor license holders: configs, AI skills, SEO templates

Guides

Your first project in Contextadmin: from installation to a running application

The best starting point is a specific task. You have a website to fix, an idea for an application or a store that needs a new feature. Contextadmin gives you a place where you bring together the code, the conversation with the agent and the running environment of that project.

Start with the place where you will work

You install the panel on your own VPS or a computer running Linux with systemd. On Windows, you can use WSL. When choosing a machine, consider the applications and databases you want to run at the same time. Resources that are enough for one website may turn out to be too little for several stores.

Choose a license that fits how you will use it: local work, publishing on a server or providing panels to clients. After purchase, follow the installation guide, activate the panel and add your own AI accounts.

Start the application before the first change

Add an existing project directory or use a template. Do the first start from the panel, so that port and publishing configuration is handled together with starting the containers. Open the application and check the logs. It is good to know the starting state before the agent begins changing the code.

Name the task and define the result

Create a context, for example “Optional phone number in the form”. Choose an AI account and describe the change along with how to check it: “Add the phone number as an optional field. The form must also submit without a number. Test this case.”

With a description like this, it is clear what should be built and how to assess the result. If there are constraints, state them right away: elements that must not be changed, the required look or how an integration should work.

Finish the task with a check

Review the code, run a test and open the changed view. Note in the context what was done and what still needs a decision. You can start the next topic in a new context and leave this one as the history of a specific change.

When you need approval, share a preview with the client. After sign-off, prepare the production release separately. This way, every task has a clear start, result and next step.