Context & Agents · Applications
Application detail
Manage one application's source, versions, file summaries and linked knowledge bases.
Manage one application’s source, versions, file summaries and linked knowledge bases.
An application’s page is its home. It tells you what the application is and whether it is ready, shows how far Next has got with summarising its files, lists everything the version on screen can draw on, and lets you add or replace source code.
This is where you upload code for Next to read, choose which version everyone sees by default, and record which knowledge bases belong with the application.
Before you start
- Open Context & Agents → Applications and select an application. See Applications.
- You need permission to change applications to add, replace or rename repositories, make a version the default, retry a failed version and link knowledge bases. Without it, you can still read everything on the page.
- Source is uploaded as a zip file. If your code is on GitHub, the archive download works as it is: a single top-level folder in the zip is removed automatically.
Understanding the page
What this application is
The top of the page shows the application’s name, the status and label of the version on screen, a default badge if that version is the default, and the description. Underneath are the counts for that version (files, nodes and edges), when it was processed, and the programming languages found.
The page always shows one version at a time. To switch, select a version’s name in Repositories.
File summaries
After the source is read, Next writes a short summary of what each file is for. The strip below the title shows how far that has got.
| Label | What it means |
|---|---|
| Summaries ready | Every file has a summary. |
| Writing summaries | Next is writing them now. A count such as 120 of 400 shows progress. |
| Summaries queued | Waiting to start. |
| Summaries failed | Something went wrong. The reason is shown in red. |
| No summaries | None have been written, for example because summaries are off. |
The strip also shows how many summaries were reused from other uploads, and how many tokens were used, written as in · out. A token is the unit AI models count text in; more tokens means more work and cost. If summaries are turned off, the strip says Summaries are off for this version.
What is attached
What is attached lists everything the version on screen can draw on, grouped by type.
- Code Graph – select Open code graph to explore the code in the Files, Map and Relations tabs.
- Knowledge Base – select Open → to go to the knowledge base.
A dimmed row belongs to a different version.
Repositories and versions
A repository is one zip of source, such as your backend or your frontend. A version is one complete set of repositories. Inside a version, each repository appears as its own top-level folder.
Versions do not replace each other. Every version keeps its own files and code graph. The default version is simply the one the application opens on.
Each version row shows:
| Part | What it shows |
|---|---|
| Version name | Select it to show that version on this page. shown marks the one on screen. |
| Notes and date | Any notes added to the version, and when it was created. |
| Status | Ready, Queued, Processing or Failed. Runs again when this build finishes means a repository changed while the version was being processed; another run is already lined up. |
| Result | A line such as 1,200 files · 9,400 nodes · 21,000 edges, or Not parsed. Select it to see what the parse did. |
| Repositories | Each repository’s folder name, zip name and size, with Replace and Rename beside it. |
What the parse did
Select a version’s result line to open its report.
| Item | What it means |
|---|---|
| Files stored | Every file kept from the zip. |
| In a parsed language | Files written in a language Next can break down into definitions. The rest are still readable and searchable, but have no definitions. |
| Definitions | The nodes found, such as functions and classes. |
| Edges | The connections found between them. |
| Folders | How many folders the version has. |
| Parse errors | Files Next could not read properly. |
| References outside the archive | Not errors. These point at a standard library or a dependency that was not uploaded. |
| Stages | How long each part of processing took, with the total. |
| Per repository | The same counts for each repository in the version. |
Add source to an application
-
Select Add repository above the versions list.
-
Choose the Version to add it to, or choose New version… and enter a Label, such as v1.4.0. The label must be unique within the application.
-
Enter a Name for the repository, such as backend. Use letters, digits, dots, underscores and hyphens, starting with a letter or digit. This is also the folder name it appears under.
-
Select Choose zip and pick the zip file.
-
Enter any Exclude files patterns, one per line, for files to skip every time this repository is built. This is optional. You can name a folder (tests), a file type (*.min.js) or a path (frontend/dist/*).
-
Select Add repository.
A message confirms the upload. The version is processed in the background.
If you give the repository the same name as one already in that version, you are asked whether to Replace its zip instead.
Replace or rename a repository
To replace a repository’s code with a newer zip:
-
Select Replace beside the repository.
-
Choose the new zip and confirm.
The version is rebuilt from all of its repositories. Summaries are reused for anything that did not change.
To rename a repository:
-
Select Rename beside the repository.
-
Enter the new Name and select Save.
The folder moves with it, and the version is rebuilt.
Choose the default version
-
Find a version with the status Ready that is not already the default.
-
Select Make default.
The application now opens on this version, and the Applications list shows its counts.
Retry a failed version
- Find the version with the status Failed.
- Select Retry.
If it fails again, open its result line to see the parse report, or check that the zip contains the code you expected.
Link knowledge bases
The Knowledge bases section records which document collections belong with this application, such as its design documents or support runbooks. Links are grouped as Every version or Pinned to one version.
- Select Link knowledge bases.
- Choose a Knowledge base or group. Choosing a group links every knowledge base in it; any already linked are skipped.
- Choose what it Applies to:
- The whole application — every version, which also covers versions uploaded later. This is usually what you want.
- Only a named version, for material that only applied to that release.
- Enter a Note explaining why it belongs here. This is optional.
- Select Link.
A version’s knowledge bases are the application-wide ones plus any pinned to it. Pinning never takes one away.
To change a link’s note, select the Edit note icon beside it. Only the note can be changed; to change the knowledge base or version, unlink it and link it again. To remove a link, select the Unlink icon and confirm with Unlink. Unlinking touches nothing else: the knowledge base and the application are unchanged.
Change application settings
Select Settings in the top-right corner. It takes you to Governance → Applications, where the name, skipped file patterns and summaries are managed. See Governance: Applications.
What to expect
- Processing runs in the background. You can leave the page and come back.
- A link that names a version the application does not have shows the default version instead, with a message saying so.
- Document Centres are not available yet. appears under What is attached; this is expected.
Good to know
- Take the tour. The help (?) menu in the top bar replays this page’s guided tour.