Building with Senova Code
Hand Senova a feature or a fix, stay in control of what it changes, and ship it.
Lesson 1 · 4 min
Start a session
Open Code and describe what to build. Senova starts in a new empty folder, or open an existing project or clone one from GitHub.
Your code runs in your own isolated cloud machine with a real terminal, Node, Python and git: not on Senova's servers and not on your laptop.
Lesson 2 · 4 min
Choose how much it asks
You decide how much Senova does on its own. It can ask before every change, accept edits automatically, or only plan. Whatever you choose, it keeps to the project's folder and treats secrets as off limits.
Tip Start with asking before edits on an unfamiliar project; switch to accepting edits once you trust the direction.
Lesson 3 · 5 min
Review every change
Files, Changes, Terminal and Preview sit beside the chat. Changes shows the exact difference for every file Senova touched; keep it or undo it in one click. Preview runs what was built so you can try it.
Lesson 4 · 4 min
Work with GitHub
Clone a repository into the session, work on a branch, and open a pull request without leaving Senova. Review the pull request as you would any other before it's merged.
Lesson 5 · 3 min
Spec first, when it matters
For bigger changes, turn on Spec first. Senova writes a short spec, asks you to approve it, then builds and checks its work against it.