Skip to main content

Projects

A project is where Jaah works: usually one or more repositories, or, with none connected, work outside a codebase. The Projects page lists every project shared with you. Open it from the sidebar: select Directory, then the Projects tab.

The list​

The Projects list on a phone: three projects, each with its eye, its Questions count and a ⋯ menu

Each row shows, from left to right:

ItemMeaning
EyeShown or hidden, for you. Select it to Hide or Show the project. A hidden project stays here, greyed. See Hide.
ProjectThe project's name. If you can edit it, select it to open its settings.
QuestionsTasks waiting for someone's answer. Not shown beside an open project.
RunningTasks running now. Not shown on a narrow list.
QueuedTasks waiting for a slot. Not shown on a narrow list.
SlotsSlots in use now. Not shown on a phone.
⋯The row menu. See Row menu.

Point at a count to see it in words; — means you can't see it. The task counts leave out features you hid. Select a column's heading, or the sort button beside New project (or Add project), to sort by it.

An empty list reads No projects yet, with New project (or Add project) under it, or No projects visible if you can't create projects: none is shared with you.

Row menu​

A project with more than one repository names them when you point at its name, or tap its dot on a phone: how many, then each one, the primary first.

Select ⋯ on a row.

A row menu: Hide, GitHub, Edit and Delete

ItemWhat it does
Hide / ShowAs the eye.
GitHub, your forge's name, or RepoOpens the primary repository. Shown only when the project has a repository.
EditOpens the project's settings. Shown only if you can edit the project.
DeleteDeletes the project after you type its name and select Delete, together with its tasks (running ones are stopped) and every slot it has (each slot's folder is erased on its node). On an Easy Mode project whose app has an address, you type that address instead, and the app is deleted too; its repository stays. Requires the org admin role.

Add a project​

Select New project (it reads Add project once you have a Git account connected; + while a project is open beside the list). Shown only to an Org Owner, an Org Admin, or a Project Maintainer granted on the whole organization, who becomes Maintainer of the project they create; anyone else opening the page's address sees No access to that page. The screens below are an org owner's.

The New project page on an existing app's Details step: the step bar, Repo URL and Name, then Cancel, Back and Create project

The New project page walks through steps under a step bar (on a phone, Step 1 of 3 and the step's name). Each question is a list of answers, one per row, each with a line under it on when it fits best. Clicking an answer moves on; one picked with the keyboard waits for Next. Back returns a step with the answers kept.

  1. What are you making? App / Website (building software or a site) or Business / Sales / Marketing Initiative (sales, marketing, research or other business work, no coding needed). A business initiative is always new: it skips the next step.
  2. Is it new or existing? (an app only) New or Existing.
  3. Details, headed Tell us about your app, Tell us about your initiative or Connect your repository: the fields the answers need, then What happens next (what Create starts), Cancel, Back and Create project. A new app asks What kind of app? here: Web app (runs in a browser, hosted by Jaah; picked to start) or Something else (mobile, desktop, scripts).

Once Create a new repository has made a repository, New and Business / Sales / Marketing Initiative are off.

AnswerFieldsWhat Create makes
Web appName, Address, Describe your appA private repository in Jaah's GitHub organization, made from Jaah's web app starter, with main and develop, its app hosted at the address, a Dev version of it at its Dev address (the address with --dev after the name, with its own empty database), and a started build epic: the App Wizard asks about the app in plain words, then the first version is designed, planned and built. The page opens the project's tasks, with that epic highlighted (Your first epic).
Something elseNameA private repository in Jaah's GitHub organization, with main and develop and a README.
ExistingRepo URL, NameNothing: the project uses your repository.
BusinessName, Describe the initiativeA private repository in Jaah's GitHub organization, with main and develop and a README, and a started Business Wizard task: it interviews you in business words, then records the activity in the repository for later tasks and files the first jobs as drafts. The page opens that task.

Every other setting starts at its default and is changed afterwards in the project's settings, below. Its tasks run on the first free engine (Any) until a Default agent is set in General. Your answers are written at the top of the project's Agent instructions, so its agents know what it is.

FieldMeaning
Repo URLAn existing app: the Repo URL and Integration branch, as in Settings › General. Add another repository adds more; the first is the primary unless you make another one primary. Create a new repository makes one instead, as in Settings › General. Required: until one is entered, Create project stays off and pointing at it says Pick your repository. With no Git account connected, or none that still works, the line No Git account connected. Connect one to pick a repository, or paste its URL. comes first, with Connect: it opens the New Git account page (see Profile), and once the account is connected you come back with your answers kept and its repositories listed. Cancel there comes back with nothing added. When a connected account's repositories can't be read, the line under the field says Couldn't read your GitHub repos (or your forge's name) and what to do.
NameRequired. The project's name, and its repository's for a project Jaah makes. Picking a listed repository as the primary fills it in, until you type a name yourself.
Describe the initiativeA business project only, required: what it is, who it's for and what you want done, up to 4,000 characters. The Business Wizard starts from it and does not ask again what it already says.
AddressA web app only: the address the app will get, shown once you type a name.
Describe your appA web app only, required: what it does and who it's for, in your own words, up to 4,000 characters. The App Wizard starts from it and does not ask again what it already says.

The page names no nodes: a new project runs on All, every enabled node of your organization, and each task gets its own fresh copy of the repository on the node it starts on. If no node is online, the page says No node is online. Tasks wait until one is., with New node where you can add one: it opens the New node page and comes back here with your answers kept. To keep the project on some nodes only, pick its Node groups later in Settings › Nodes. A new web app in an organization with a shared node runs on that node instead.

With no model account in the organization, a warning says no agent is set up and the task waits for one, with Add account.

Create project (reading Creating… meanwhile) creates the project. If you may create and start tasks, it also starts the first task, and What happens next above the buttons says so: the initial setup and deployment of an app, or the setup of a business initiative, with questions the task may ask you. On an existing repository, Create first creates each new repository and sets up an empty one on its forge, so a refusal shows on its row. A web app opens the project's tasks, where Your first epic points at its App Wizard epic and says what to expect; its app reads Setting up until it is live. A business initiative opens its Business Wizard task. Something else opens the project; its onboarding task asks what the project is about, never again what you answered here. An existing app opens the project's tasks with the onboarding task selected. A placement warning opens the project on Settings › General instead. A refusal, such as the plan's app limit or a name already taken, shows above the step bar.

Cancel goes back to where you opened the page from, or to Projects. The project is not saved before Create project; leaving with values entered asks This project is not created yet. Create it before leaving?

A project's settings​

Select a project's name, or Edit in its row menu. The project opens beside the list, in tabs: Settings, which opens first, Schedules (for anyone who can see the project's schedules), Production QA (only where the plan includes Production QA), Benchmark (only while the organization's benchmark mode is on), and Budget (requires the org admin role, and a plan that includes budgets). The tabs that don't fit the strip's width are under More ▾, which takes the name of the open tab when that tab is one of them. The same Settings opens on the Tasks page, under its Settings tab, while the project is picked in the sidebar.

A link to one section of Settings reads like /projects/12?tab=settings&section=variables. A link that names a section as its tab, such as ?tab=variables or ?tab=general, opens Settings at that section; ?tab=pipeline opens CI Pipeline, ?tab=slots Nodes, and ?tab=advanced General with Advanced open. ?tab=automations opens Schedules. One to Merge lane or Memory opens Audit › Merge lanes or Audit › Memory, filtered to the project.

To rename the project, select its name at the end of the trail above the tabs, type, then press Enter or select elsewhere: it saves at once. Escape keeps the old name; an empty name is refused. Without the right to edit the project, the name is plain text.

Settings ends with Cancel and Save under the section shown. They save General, Branches, Memory, Merge lanes and Testing at once, while Access, CI Pipeline (with the custom pipeline under it), Issue trackers, Live Cast, MCP, MicroVM and Nodes save on their own. Each variable saves from its own page, opened from its name in Variables. Leaving the page with unsaved changes in the sections Save covers asks first; moving between sections keeps the changes. A section or tab with its own Save loses unsaved changes when you leave it.

Hover a field's dotted-underlined label, or tap it on a phone, for what the field does.

A project Jaah manages​

A project on a repository Jaah made for it, in Jaah's own GitHub organization (every web app Jaah hosts, and any project created without a repository), is Jaah's to run. Its page shows you only Settings, with its General, Variables and Issue trackers sections (and Access unless your plan allows one user), and Budget (where shown above). General keeps the stage addresses, the Repository line, Default persona and Agent instructions, and under Advanced the Default agent and, for a web app, its usage; its branches and routing are hidden, as is its repository link in the project list. The Repository line reads the repository's name followed by at Jaah. Transfer, shown if you may edit the project, opens an empty repository editor to put the project on a repository of your own: add yours, then Save asks what happens to Jaah's (see Repository). Once it is on yours, every tab and section comes back.

On a project with a repository, other than one Jaah manages, a line above the tabs says when tasks you start could not push with your own Git connections:

LineMeaning
Tasks can't push here.None of your Git connections can push to the repository or open a pull request there. The line names what is missing; Fix, when shown, opens the place to fix it.
Tasks push as a connectionYour selected GitHub connection can't write to the repository, so your tasks push as the connection named instead.

With neither line, your tasks push with your selected connection.

If you open a link to a project that belongs to another of your organizations, the page says This belongs to that organization and offers Switch to it. Nothing switches until you select it, and the organization may ask you to sign in again. A project you can't reach in any of your organizations shows Project not found.

Settings​

The project's settings, as in System Settings: a list of sections on the left and the one picked beside it. General comes first, then, from A to Z, Access, Branches, CI Pipeline, Issue trackers, Live Cast, MCP, Memory, Merge lanes, MicroVM, Nodes, Testing and Variables (Branches, Merge lanes and Testing: Branches, Testing and Merge lanes). General shows until you pick another. On a phone the list comes first; a section opens in its place, with ‹ Back to the list. A section in use shows On in the list and ● On beside its title: a ticked box, or any setting changed from its default. Search settings, above the list, finds a setting by name: while you type, the results take the place of the list and the section, each with its section's name, and matches only in a setting's help come after Other matches. Picking one opens its section and highlights the setting; with nothing found it reads No matching settings. On a phone it shows above the list, not inside a section. A section whose feature is not in your edition or plan is left out; Branches, Testing, Merge lanes and CI Pipeline show only on a project with a repository.

The Settings tab with Branches picked: the list of sections, then Read only, Branch prefix, Integration branch, Allow force push and Squash task PRs

General​

The first section of Settings. It saves with the Settings Save.

General: the Repository line, Default persona, Agent instructions and the closed Advanced section

From the top:

FieldMeaning
App stateOnly on a web app Jaah hosts, while it is not live: its state, such as Setting up, Paused or Deleting. It updates by itself while the app is setting up or being deleted. A failed setup reads Setup didn't finish. Try again in a few minutes. with Retry if you can edit the project; otherwise Setup didn't finish.
Stage addressesOne line naming each pipeline stage that has an address, with the address after it: Dev: an address · Production: an address. Each address opens in a new tab. Not shown when no stage has one.
RepositoryThe repositories the project works in, on one line: each name with its forge's icon beside it, then Add. With two or more, Primary marks the one the gate, stack and ports run in. With none, it reads None and Add. See Repository.
Default personaThe persona a new task in this project starts as, such as Marketer for a sales project. It also applies to tasks agents file without naming one, and to an epic's subtasks the planner doesn't assign. Org default uses the Persona set in Settings › Tasks › Defaults. You can still change the persona on any task.
Agent instructionsText given to every agent that works on this project. Where it disagrees with Jaah's own procedure, it wins. Anyone who can view the project can read it: never put a password or token in it.
AdvancedThe rest of the fields, closed each time you open the page. Select it, or press Enter or Space on it, to open it. A field there with an error opens it. See Advanced.

A web app Jaah hosts shows its stages' release status in CI Pipeline.

Repository​

Select a repository's name to edit it in place, under the line:

ItemMeaning
Repo URLLists the repositories your connected Git accounts reach, grouped by owner: type to search, or paste any address. A Forge list appears when Jaah can't tell the forge. Create a new repository makes a new one instead: pick its Owner (an account, organization, group, workspace or project your Git accounts reach; one Jaah can't create in shows why) and its Repository name. It is created private, with main and develop, when you save; Use an existing repository goes back. Shown only if you can create projects.
Integration branchThe repository's integration branch. The primary's is the project's integration branch: changing it needs the right to change Settings › Branches.
Set primaryMakes this repository the primary. Shown on a repository other than the primary, when there are two or more.
✕Removes the repository. The primary is removed last, or after another is made primary.
Done, CancelClose the editor, keeping or dropping its changes. Escape cancels.

Add opens the same editor, empty. Changes join the page's Save and Discard.

With no repository, the project works outside a codebase: tasks start in an empty slot and the repository-only fields in every section are hidden, keeping their values for when one is added. Removing the last repository stops tasks running in its slots; they start again without it.

Replacing or removing a repository Jaah made for the project asks first, on Save: Move the code and history to the new repository? (Yes / No) when the project has a finished task and the new primary is yours, else Switch repository? or Remove the Jaah repository?. Either way Jaah archives its repository and turns off the project's app; with an app running, you type its address first. Yes starts a task that moves the code and history into your repository (pushed as is when it is empty, else on a new branch with a pull request), then archives Jaah's; a toast links the task. Cancel saves nothing.

Advanced​

General with Advanced open: Default agent, Default model, Routing, Run jobs as and Tech stack

FieldMeaning
Default agentThe agent a task runs when the task itself picks none. Any runs it on the first free engine. See How agents work.
Default modelThe model tier used when neither the task nor its persona sets one.
RoutingHow tasks pick their runner: Mode (Off, Recommend shows the router's pick on each task, Auto runs on it), Latency cap (the most hours a routed task may take; empty, no cap), Experiment budget (the share of 30-day spend for trying other runners and benchmarks), Blind review (on major and security changes, other agents review the pull request without its author's reasoning; a line under it says why it can't run yet, such as no node of the project being able to) and Prefer a different vendor (with Blind review on, the reviewer comes from another vendor than the author where one is allowed). A mode above what the organization allows can't be picked. Needs intelligent routing in the organization's plan; otherwise, or where routing is off for the organization, the section is hidden unless the project still has a mode or Blind review on. Shown once the project exists.
Run jobs asThe person whose Git access the project's background jobs use: the outcome scan, the merge lane's own tasks, benchmark reviews, and tasks an automation, schedule or trigger files without a person starting them. Org default uses the organization's choice in Settings › General › Background jobs, else its first owner or admin. An automation's own Run as comes first. Jaah skips a pick with no working Git connection to the project's forge and takes the next who has one. Once saved, Runs as under the field names who the jobs run as. When that person can't push or the pick was skipped, No GitHub login (or your forge's name) follows it: point at it for why, select it to open your Git connections in Profile. Shown to anyone who can edit the project; a Maintainer can pick only themselves.
Tech stackOne row per part of the stack: a name and what it uses. Add adds a row; × removes one.
NotesFree text about the project.
Requests, EgressOnly on a web app Jaah hosts: this month's requests and outbound traffic, against the plan's limit.
DatabaseOnly on a web app Jaah hosts: the database's size, against the plan's limit.
ConcurrencyOnly on a web app Jaah hosts: how many requests the app may serve at once.
Hosting endsOnly on a web app Jaah hosts: the day your plan's app hosting ends (free hosting, when Jaah sponsored your organization); the app pauses then. Shown only when it has an end.

Variables​

A section of Settings: variables written into a slot's settings file when a task claims it.

Settings › Variables: No environment variables, Add variable and Show preview

The list has one row per variable; a name with both an Everyone value and an Only me override has two rows. A narrow screen keeps the name and the value.

ColumnMeaning
NameThe variable, after a mark: ✓ on the row whose value your slot gets, ! when it doesn't resolve, – on any other row. Point at the name or the mark to read: why it doesn't resolve, what writes the name instead, Set by the person for another user's override, and its description.
ScopeProject default, Your override or Another user’s override.
SourceCredential, Literal or Port.
ValueThe literal, the credential and field it reads (never a credential's value), or, on a Port variable, auto or prefers and its number.

Before any is added, the section reads No environment variables.

Select Add variable to add one, or a variable's row to open it; one you can't change opens read-only. Each opens on its own page beside the list, with Cancel and Save (Create for a new one); Delete is in the page's menu.

What each field on a variable's page means is on Project variable.

Select Show preview to see the values your own slot would get.

Branches, Testing and Merge lanes​

Sections of Settings, shown only on a project with a repository. Branches, Testing and Merge lanes hold these fields:

FieldMeaning
Branch policy forWhich repository the Branches fields below apply to. Shown only with two or more repositories. In General, the shield beside a repository's branch opens Branches with that repository picked.
Read onlyOn: runners can work in the repository but never push to it.
Branch prefixPut in front of every branch Jaah creates. Leave it empty for none. With a prefix, Jaah pushes and opens pull requests only from branches under it. Off while Read only is on. On a custom pipeline the primary repository's is also its building stage's branch in the custom pipeline: a change in either place shows in both.
BranchThe repository's integration branch, where pull requests land. The same value as the repository's branch in General: change it in either place.
Allow force pushLets runners push straight to the integration branch, for example to rewrite its history. A runner asks you first in the task; your yes lasts the rest of that task. Off while Read only is on.
Squash task PRsFor the whole project. On: each task's pull request merges into the integration branch as one commit named after the task. Pull requests from bots, people and releases keep merge commits. The repository must allow squash merging.
Quick gate commandThe fast check runners run as they work. Keep it fast. Empty: no quick gate. A new project starts with your organization's default, set by Jaah.
Full gate command / Full gateThe full check, run before a change merges. On a basic pipeline you type it in Full gate command; empty means none. On a custom pipeline Full gate shows Open CI Pipeline → Merge gates instead: it is the Merge step's gate in the custom pipeline, as hovering the label says.
Stack up commandStarts the project's local stack in a slot. Empty: no stack. A new project starts with your organization's default, set by Jaah.
Stack down commandStops it. It must stop containers only, never delete data. Empty: none. A new project starts with your organization's default.
Outcome scan intervalHow often, in minutes (15–1440), Jaah scans the repository for reverts and fixes of merged work. Blank uses the organization's value, or Jaah's default. Shown, with Security checks, once the project exists and only where the plan includes agent performance.
Security checksThe CI checks that count as security scans, separated by commas. The usual scanners always count.
Merge lanesOn: runners' pull requests queue for the merge lane, which tests them together and merges them. Off by default. Off your plan, the box is disabled with Upgrade subscription to activate. A line under it says when the lane can't run here (for example, Read only is on or the forge can't merge a pinned commit). While it runs, Audit opens Audit > Merge lanes for this project. Turning it off stops new pull requests from queuing; those already queued still finish.
Batch sizeIn Merge lanes, while it is on: how many pull requests the merge lane tests and merges together.

Commands are not secret: anyone who can view the project can read them. Never put a password or token in them.

For anyone who can edit the project, Testing's Outcome scan also shows Last scan (with Stale when overdue), Cursor, Interval and, while one runs, Scan running, a link to its task. Scan now starts a scan; a line beside it says why when it can't.

CI Pipeline​

A section of Settings, shown on a project with a repository: it picks the project's pipeline. It has its own Save pipeline, with Discard, once you change something.

Settings › CI Pipeline on a basic pipeline: Custom pipeline off the plan, Integration + Release picked, the release branch and addresses, then Deploy tracking reading Not connected.

FieldMeaning
Custom pipelineYour own stages, steps and rules. Once saved, they are edited below the box: see Custom pipeline. Off your plan, the box is disabled with Upgrade subscription to activate. Saving a basic pipeline over a custom one asks Replace the custom pipeline? first.
PipelineWithout a custom pipeline: PR into integration branch (merging a pull request deploys to the live stage) or Integration + Release (merging deploys to Dev; a release moves it to the release branch and Production).
Integration branchEach repository's, read only; Edit goes to General, where it is set.
Release branch, Dev addressOn Integration + Release: the branch a release moves Dev's code to, and where Dev runs.
Production addressWhere Production runs.
Deploy trackingOn a saved basic pipeline: Not connected. or each connection, and, until connected, the workflows that deploy Production (Workflows to add on GitHub; the other forges' fields are as in Production QA) with Connect. Until it is connected, a release reads Released as soon as its pull request merges; once connected, it stays Releasing until that deploy run succeeds.

On a custom pipeline the same Deploy tracking sits under the Production stage's deploy target, in the custom pipeline.

Custom pipeline​

Under the Custom pipeline box, once a custom pipeline is saved: the project's stages and the steps between them, with their own Discard and Save. Only someone who may edit the project can change them. Saving works while a release runs: Applies from the next run shows under Save, and the running release keeps the settings it started with. How to use it: Set up a project's pipeline.

ItemMeaning
StagesA row of cards, by default Ideas, Building, Dev and Production. Each has the same fields: its name (select it to rename), Branch and Address. + on an arrow, or at either end, adds a stage there; pointing at a card shows ‹ and › to move it and ✕ to remove it. Any stage can be removed; one stays. Branch empty: work moves to the stage; a pattern such as fleet/*: work is built there, and its prefix is the project's branch prefix; a branch name: work merges into it, and the first one is the project's integration branch. A refused save shows its reason on the card it names.
Start from…Beside Stages, for someone who may edit the project. A preset… or Copy from project… opens a list, each choice with its stages; picking one shows What changes, and Use this fills the stages and steps as unsaved changes. Nothing is saved until Save. How to use it: Start a pipeline from a preset or another project.
Link to template…Beside Start from…. Pick a published org template, review what changes, Link. While linked, the section reads Linked to template name · version published date with Unlink; stages can't be added, removed, renamed or moved; locked fields show a lock and Set by template and can't change; a changed open field shows Changed here with Use template value; Start from… is unavailable. How to use it: Link a project to a template.
StepsOne panel per step into each stage after the first, all with the same settings; its header names what it does (Move, Start, Start and merge, Merge or Release), the two stages and a summary of its rules, and opens it. Who: Can press (roles and members; until changed, whoever may do it by default), Runs (By hand or By itself). Gates (merge and release steps): the checks the step runs first, in order, each Required or Advisory; how to add one: Add a gate to a pipeline step. Approvals: Needed (0 to 5), Approvers, Requester can't approve, Approval timeout, On timeout, Instructions for approvers. Timing: Wait after arrival, Allowed hours. Concurrency (release steps): Order, Newest wins or In order. Paused with Resume while the step is paused by itself. Each setting: Set up a project's pipeline.
Deploy trackingOn the Production stage: whether its deploys are recorded. Until connected, a release to Production reads Released as soon as it merges; once connected, it finishes when its deploy run succeeds. How to connect it: Set a stage's deploy target.
FreezesFreeze now stops every release after the integration stage at once, until cleared. Times when no release starts; a scheduled one waits for the freeze's end. Add freeze adds one: Name, Starts, Ends, Repeats (never, daily, weekly, monthly), Stages, Let through (hand-pressed steps, releases already queued) and Remove. Each: Freeze releases.

Access​

A section of Settings: who can reach this project, and with which role.

Settings › Access: a Filter box, Grant access, and the list of members with their Source and Role

Filter narrows the list. Select Member, Last active or Role to sort by it. Expires and Last active show only on a wide window; on a narrow one, point at a row to read them. Each row is a person or a group; its dot is green while the access holds and reads Expired once it has ended.

ColumnMeaning
MemberThe person or group. A group shows how many members it has; open it to list them.
ExpiresWhen the access ends, or Never.
Last activeWhen they last used Jaah.
SourceHow they hold it: Direct, Via a group, or From the organization or a parent. A link opens where it comes from.
RoleThe role they hold on this project.
⋯Remove takes away a direct grant, after you confirm. A grant held through the organization or a group offers Open org to remove or Open group to remove instead, a link to where it is removed.

To give someone access, select Grant access. Shown only if you can manage who has access to the project.

The Grant access dialog: Who, Role, Expires, with Cancel and Grant

  1. In Who, pick one or more people or groups.
  2. Pick the Role.
  3. Optionally, pick a date in Expires. Left empty, the access never expires.
  4. Select Grant.

MCP​

A section of Settings: the MCP servers this project's agent sessions reach. A connection must be linked here; being visible to the project is not enough.

  • To link one, pick the MCP connection, then select Link.
  • To remove one, select Unlink on its row. It stays attached to the project.

A Google Antigravity session in the terminal runtime gets no linked server; on ACP it does.

MicroVM​

A section of Settings, shown where the plan includes MicroVM: the size of the virtual machine a task of this project runs in, where its node runs tasks in MicroVMs, and which internet names that machine may reach. Adding or removing a name saves at once; Edit size has its own Save and Cancel.

MicroVM's Size section: vCPUs, RAM and Disk, each from system

ItemMeaning
vCPUs, RAM, DiskThe size in force, and where it comes from: from system, from org or from project. A node's own size overrides the project's.
Edit sizeOpens this project's own values, with Save and Cancel. A field left empty (Inherit) keeps the value from above; each takes a whole number. Shown only if you can edit the project.
VMs reachHow many internet names the machine may reach.
AddedNames this project adds. Type one in Add a name and select Add; × on a name takes it off.
RemovedDefault names this project blocks. Type one in Remove a default name and select Remove; × on a name allows it again.
DefaultThe names every project's machines may reach. A name this project removed is struck through.

Live Cast​

A section of Settings, for anyone who can edit the project. Without Live Cast on the plan, its box is off with Upgrade subscription to activate. Ticked, it publishes the project's tasks and artifacts to a public read-only page. It has its own Save, shown once you change something, and Publish. How to use it: Publish a Live Cast.

ItemMeaning
Live CastTurns Live Cast on for this project. While it's off, nothing else is offered and nothing can be published.
Publish by defaultAll shows every task unless a rule hides it; None shows only the tasks a rule picks.
Hide those that / Show only those thatThe rules, one per line. + Add rule adds one, × removes one.
Publish / UnpublishPublishes the settings, or takes the public page offline. While published, the settings are locked.
LinkThe public address, with Copy link, once published.
EvaluatedHow many items the rules have checked, out of all of them.
Tasks aren't being checkedShown when nothing can check tasks, with Ask an operator to turn on task checks.

Issue trackers​

A section of Settings: the tracker connections this project links, with their tracker projects. Add link, Edit, Remove, Make primary where another project shares one, and Auto-start imported tasks per link (off: a task an issue starts waits as a draft). Each change saves on its own. A member of a project Jaah manages sees it too. See Link a project to an issue tracker.

Memory​

A section of Settings, shown once the project exists, when your organization's plan includes project memory. Project memory sets whether the project's tasks may draw on what earlier tasks recorded: On or Off. Default follows System Settings, and its label shows which, such as Default (On). Tasks have no setting of their own. It saves with the Settings Save, and the list shows On while it is set to On here. See Audit > Memory.

Nodes​

A section of Settings: which nodes run the project. Node groups is All (every enabled node of your organization), or the node groups you pick, one chip each. Picking a group replaces All; removing the last one puts All back. Both apply at once, with no Save, and a change that takes nodes from running tasks asks first; running tasks finish where they are. Under it, Runs on names the nodes the project's tasks can start on now, each a link to its node, an offline one marked (offline), past eight as and a count more; with none it reads No node runs this project. Where you can't change the field but may edit nodes, Change beside it opens the Machines page. On a plan without node groups it reads All, with Choosing node groups is on the Business plan. and a link to Billing for an org admin; groups kept from an earlier plan show Not active on your plan. Changing it needs the right to edit the project. See Run a project on some nodes only.

Schedules​

The automations that apply to this project: those whose Target names it, or takes every project, and those with no target. A project's Maintainer sees, and can make, only the schedules whose target names projects they maintain, and changes only their own. The Tasks page's Schedules tab shows the same list while the project is picked in the sidebar. The list, its filters and its row menu are those of the Automations list. New automation opens one with this project already its target. With none, the list reads No automations for this project.

Production QA​

Shown only where the organization's plan includes Production QA. It records the project's releases, watches each production release for a regression, and files tasks from what it finds. How it works: How Production QA works; turning it on: Turn on Production QA for a project. It has its own Save, with Discard once you change something.

Connect releases shows whether the forge sends releases to Jaah (Not connected., or each connection). Until it is connected, it asks which workflows release (Workflows to add on GitHub, the CI config file on GitLab, Pipelines to add on Azure DevOps, the Production branch and Release statuses on Bitbucket). On GitHub the field comes filled in with the workflows that run on a push to the Production branch, and a repository whose Pages build from the branch connects with none. Connect saves them. On GitHub Jaah then adds the webhooks itself, or says what to do: Install app, or Set up manually to add them yourself; on any other forge it shows the webhooks to add, their secrets shown only then. On Bitbucket, org admins connect releases. Connecting needs the right to edit the project.

ItemMeaning
Production QATurns it on for the project: tasks are filed from incidents and probes run. Releases are recorded either way. Off for this org when the organization can't turn it on.
Release workflowsThe workflow files whose runs count as releases, one per line (Release pipelines on Azure DevOps; not shown on Bitbucket). The one list that counts: Connect releases adds what it connects to it.
Revert policyWhat a regression files: Off, nothing; Draft, a draft task; Auto-file, a task that starts.
Window (min), Min eventsUnder Regression: how many minutes after a release are measured, and the fewest events worth measuring.
Error rate ×, p95 latency ×The multiple of the before-release value that counts as a regression.
Health URLsUnder Probes, run from a node after each production release: Add URL adds a Name, URL and Expected status; up to ten.
Smoke commandsAdd command adds a Name, Command and Timeout (s); up to five. Remove takes a row off.
AutomationsThe project's Production QA automations, each with its trigger and status. Create defaults makes them when there are none. Org admins manage them.

Benchmark​

Shown only while the organization's benchmark mode is on. It has its own Save, with Discard once you change something.

ItemMeaning
Benchmark modeRe-runs a sample of the project's merged coder tasks on another configuration. Their pull requests never merge.
Sample rateThe share of merged coder tasks re-run, as a percentage.
BudgetThis month's benchmark spend out of its cap, with Budget reached once nothing more is sampled this month. The cap is the Experiment budget under Routing in General.

Budget​

Requires the org admin role, and only shown when the organization's plan includes budgets. How much this project's tasks may spend in a month.

ItemMeaning
Monthly budgetThe limit, in dollars. Save sets it; Remove takes it off.
Spent this monthBelow the field: what the project has spent this month, out of the budget and as a percentage, or No budget. Near limit shows as it gets close.
Budget reached — new tasks wait.The banner once the project has spent its budget.