Skip to main content

Projects and your code

A project is what code an agent works on, plus the settings that belong to that body of work.

The two kinds of project​

From a Git repository​

Needs a Git connection. You choose the repository and the branch to check out; every runtime launched for the project clones it and starts on that branch.

The agent inside the container uses the connection's access to clone, commit and push, so branches it creates appear on GitHub where your team can review them. PlatformSmith never deletes or force-pushes your code on its own.

From a base image​

No repository, no Git connection needed at all. The container starts from an image and that is the whole story. This is the right shape for experiments, scratch environments, evaluating the platform before granting repository access, and any workflow where the code arrives some other way.

Both are first-class. You do not have to "upgrade" a base-image project to a repository one.

Scratchpad — the one you already have​

Signup creates a project named Scratchpad in your first workspace: a base-image project with no repository, there so your very first launch needs no setup at all. It is gitless on purpose — a repository-backed project would need a Git connection, a repository link and a branch first.

It is an ordinary project in every other respect. Rename it, delete it, or attach a repository to it; none of that is special-cased. Just remember that with no repository behind it, nothing an agent writes there is pushed anywhere.

Creating a project​

Projects → New project, then pick a source. A project belongs to exactly one workspace and cannot be moved between workspaces — if you need it elsewhere, create it there.

What a project scopes​

  • Agent definitions at project scope, which override workspace and organization definitions.
  • Secrets at project scope, which take precedence the same way.
  • Its runtimes, sessions and playbook runs — its history.

Precedence across the three scopes is on Configuration precedence.

Choosing a branch​

A repository-backed project checks out a branch when a runtime is provisioned. Point long-running work at a stable branch, and let agents create their own branches for changes — that way a review happens on GitHub, where your team already reviews things.

Private repositories​

A project can use a private repository as long as the Git connection has been authorized for it on GitHub's side. If repositories stop listing or a clone fails mid-launch, the connection has usually lost its installation — use Reauthorise on the connection.

The project nobody created​

You may see a project named platformsmith-conductor that you did not create. It appears after your first playbook run: it is a system project the platform uses to run playbook work. You do not need to configure it, and it is not a mistake.

Deleting a project​

Deleting a project takes its runtimes, sessions and history with it. Your repository on GitHub is untouched.

Last updated on