Build and change your site, read the web, make pictures, write documents. And what he hands to you.
Flexi works in your project like a developer with a browser, a sandbox and your repo, and he only does what you ask. The list, plainly.
He checks the repo out into his sandbox, changes it, and commits when you ask. Every commit goes to the one branch that deploys, shows in the chat as a card, and builds the site; Preview › Builds shows each build, and you put any of them live. He never commits a key, a .env file or installed packages.
A page mockup, a web page, a proposal, a plan, a brand guide: each lands in the chat's Files as an output you can open, and, when you ask, in the Library on its shelf. Design documents are real HTML pages: a brand guide shows its colours and type.
Paste a link and he reads the page. He can map a site's pages, read many pages of one site (importing an old site, a competitor's offer, an SEO audit), search and read for research, pull the same fields from several pages (a pricing comparison), and look up data about a company, a place or a price. What a page says is information to him, never instructions. Crawled pages are working files in Files, not the Library, until you ask to keep them.
He can screenshot a web page or a page he made, at phone, tablet, laptop or desktop width, and look at a picture or a PDF you sent. He makes pictures with an image model: a hero image, an illustration, a product shot, a social post, a logo idea, or an edit of a picture you sent. Each one costs FlexOS money, so he makes one, looks, and asks before making several. A diagram, a chart or a page he draws as HTML or SVG instead, because those are exact and editable.
Some jobs need one of your keys for one command in his sandbox: a service's command-line tool, its API. He can do that with a key from the Vault, for that one command, after you say yes by name in the message that starts the turn: Yes, use STRIPE_SECRET_KEY (the chip he offers). A plain yes is not one, and one key per yes. The key is never shown in the chat or saved.
In Connections, Set it up with Flexi opens that service's own space: he asks what it is for here, puts up one card for the missing keys, and writes the integration doc once every required key is in. The Connections article has the whole flow, the guided sign-up and the sign-up robot.
He cannot put a build live, change Settings, import a zip, ship the phone app, set up or talk to an agent, read the Inbox, read back your Tasks, sign in to a site, or watch a site on a schedule. Each of those is yours, and he says so rather than pretend. What is not there yet is the full list.