Skip to main content

​
Workspaces and projects

A Qodex project is one app or service you are testing. It contains the agent chats, saved scenarios, scripts, findings, run history, memory, environments, auth profiles, integrations, and API keys for that app. A workspace is the set of projects your team can access from the project switcher.

​
Project boundary

Use one project per app or service. If you test two unrelated apps, create two projects. If you test staging and production for the same app, keep them in one project and use separate environments. Nothing should cross a project boundary unless you explicitly configure it. That keeps findings, memory, credentials, repositories, and usage separated.

​
What lives in a project

If multiple apps share one project, Qodex memory and findings can become confusing. Keep the boundary clean.

​
Create a project

1

Open the project switcher

Click the project name at the top of the left navigation.
2

Name the project

Choose New Project. On the New project screen, enter a Project name and click Continue.
3

Choose what Qodex should do first

Pick Review my pull requests, Test my APIs, Test my UI, or Check API security, then give Qodex the repo, spec, or URL it asks for. See Quickstart for each path. You can also skip and set things up later.
Your first project starts a 14-day free trial of the Startup plan. Later projects start on the Free plan. See Plans and pricing.

​
Switch projects

Click the project name at the top of the left navigation and pick another project. The URL changes to the selected project slug, and the app loads that project’s chats, scenarios, findings, settings, and integrations.

​
Permanently delete a project

Project admins can delete a project from Settings > Danger zone. First delete all of its test scenarios; Qodex disables Delete Project while any scenarios remain. Then click Delete Project and confirm Delete project.
This permanently deletes the project and all of its data. It cannot be undone.

​
Roadmap

Workspace-level rollups are planned: cross-project activity, spend, findings, and admin visibility. Workspace-level SSO is also planned. Today, the project is the main operational boundary.

​
Next steps

Members and roles

Invite teammates and choose permissions.

Plans and pricing

See how plans apply to projects.

Projects concept

Learn why projects are the tenancy boundary.

BYOK

Configure provider keys per project.