Date: 2026-09-11 Date: 2026-09-10

Your first Nova session

Start from the right project directory, make a focused request, and review Nova’s evidence before you rely on the result.

Start in the correct directory

Open a terminal in the project you want Nova to understand:

Set-Location C:\path\to\your-project
nova

Nova uses the launch directory to determine the project root, relevant configuration, instruction files, saved sessions, and repository scope. Starting one directory too high can expose unrelated files; starting too deep can hide project-level context.

Begin with an orientation request

For an unfamiliar repository, ask Nova to inspect before editing:

Explain the purpose of this project, its main entry points, and how tests are organised. Cite the files that support your answer. Do not change anything.

A good first prompt defines:

Outcome — what you want to know or change.
Scope — the subsystem, directory, file, or behaviour involved.
Constraints — compatibility, safety, style, or files that must remain untouched.
Evidence — the tests, commands, diffs, or UI behaviour that prove success.

Refer to concrete files

Nova recognises @ file references in prompts. Use them when a specific file is central:

Explain the validation flow in the checkout form and identify its callers. Do not edit files.

File references reduce ambiguity, but they do not replace surrounding-code inspection. For implementation work, Nova should still read imports, types, tests, and related call sites before editing.

Ask for explanation before action when needed

Separate discovery from implementation if you are still deciding what should change:

Trace why expired sessions can still reach the billing page. Give me the root cause and two viable fixes with trade-offs. Do not edit yet.

Then choose an approach:

Apply the middleware fix. Keep the public API unchanged and run the targeted tests and type check.

For a straightforward, well-scoped task, one direct prompt is enough:

Fix the failing null-state rendering in the profile card, preserve the existing visual style, and run the component tests plus type check.

Watch tool use and approvals

Nova displays tool activity while it searches, reads, edits, or executes commands. Depending on the active approval mode and operation risk, it may ask before continuing. Use the approval command to inspect or change behaviour:

/approve
/approve smart
/approve manual
/approve strict

Do not approve an operation merely because it was suggested by the agent. Read the target path, command, and risk description, especially for deletion, Git publication, database changes, or external actions.

Useful session commands

The exact command set is visible through /help. Common commands include:

/context — inspect what is using the context window.
/compact — summarise a long conversation to recover context.
/model — inspect or switch the active model.
/usage — inspect usage information.
/agents — list, inspect, or switch specialised agents.
/ask — ask a side question without adding it to the main thread.
/commit — prepare a commit from staged changes.
/rollback last — remove the last conversation turn from context; side effects remain.
/exit — leave the session.

Treat /rollback last carefully: it changes conversation context, not files, commands already run, commits, emails, or other side effects.

Review the result

After Nova finishes, check the essentials:

Which files changed?
Does the diff match the requested scope?
Which checks actually ran?
Were any checks skipped or blocked?
Are there assumptions that still need validation in the real environment?

Ask for a concise answer if needed:

Summarise the root cause, changed files, and verification results. Mention only unresolved risks.

End or resume later

Nova persists project sessions. Use nova session outside the interactive UI to list archived sessions or resume one by ID. Within a long active session, /compact preserves a summary while reducing context pressure.

What you learned

Launch Nova from the intended project directory to establish the right scope.
Define the outcome, scope, constraints, and evidence in your first request.
Review tool approvals, changed files, and verification results before relying on an outcome.

Safe practice exercise

In a non-production project, start Nova and ask it to identify the main entry points and tests. Require file citations and instruct it not to change anything.

Previous: Install and set up Nova

Return to lesson 3.

Next: Explore, plan, code, verify, commit

Continue to lesson 5.

​Your first Nova session

​Start in the correct directory

​Begin with an orientation request

​Refer to concrete files

​Ask for explanation before action when needed

​Watch tool use and approvals

​Useful session commands

​Review the result

​End or resume later

​What you learned

​Safe practice exercise