Try your peg with Workpeg AI before you ship
Open your peg’s dev page, and within a minute Workpeg AI can use your new build as if it were already released. You don’t install anything and nobody has to approve it. Your work stays in test tables.
What changed
Until now, Workpeg AI only knew about pegs that were released and installed. Your work in progress was out of its reach. To see how the assistant would use a new action, you had to publish first.
Now your dev page counts as a temporary install. While the page is open, and for about a day after you last had it open, Workpeg AI treats your build as installed in that business. The aim is simple: development and production should behave the same, so what you test is what people will get.
How it works
- Run
workpeg ui serve <your-peg>/ui --fake-cloudon your computer. Your page opens athttps://<your-peg>.dev.workpeg.com. - Open the page inside a business, at an address with
/b/<business>/in it, signed in with your development account. - The page sends your build’s
manifest.jsonto Workpeg. It does this when it opens, then every hour while it stays open. - Within a minute, Workpeg AI in any chat of that business offers what your manifest declares.
- About a day after you last had the page open, the temporary install lapses on its own.
The Scaffold, the frame every peg page uses, sends the manifest for you. You don’t write any code for this, and there is nothing to switch on.
What Workpeg AI can do with your build
The same things it can do with a released peg:
- Work with your tables. It can read, change and share them, and create new ones.
- Compose. It can draft from your build’s templates.
- Run your functions. They run on your own computer through
workpeg project serve <your-peg> --fake-cloud, just as your save hooks do. - Use your summary, skills and search links, taken from the build you are serving now.
It does this whether or not the peg is installed in that business.
Safe by design
Testing against a real business shouldn’t put that business at risk. So a dev build behaves like the real thing, and stays apart from the real thing.
- Test tables only. Everything your build touches lives in its own test space, never in the released peg’s tables.
- Nothing is sent. Whatever your build composes, mail included, is filed in the test tables and never sent. The assistant says plainly that nothing went out.
- The same approvals. The business’s usual approval settings apply. Every card begins “Development install:”, so nobody mistakes it for the released peg.
- Your computer, your functions. A function action runs only when you are running it yourself. If nothing is running, it is refused.
- Who can stand in. When an owner or admin opens a dev page of the business’s own peg, the build stands in for the released one, as the next release would. It replaces only what the build offers. Anyone else’s dev build sits beside the released peg and replaces nothing.
That access is real, so use a separate Workpeg account for development, apart from the one you use for your company.
What you need
- A developer business. A business becomes one when its first peg is approved.
- Your development account, signed in.
- Your dev page open from your own computer, using the Scaffold, inside a business.
- For function actions only: serve with
workpeg project serve <your-peg> --fake-cloudinstead, which runs your function too.
Building on someone else’s peg? You can, unless its owner has closed it to other developers in the manifest.
One thing still needs a released peg
Outside-service permissions don’t work from a dev page. That’s the Allow or Don’t Allow screen that hands a key to your server. The key goes to the service address Workpeg set for your released peg, so that flow waits for release. Workpeg AI and everything above work without it.
Try it
Start workpeg ui serve <your-peg>/ui --fake-cloud and open your peg’s dev page in a business. Then ask Workpeg AI, in any chat of that business, to use one of your new actions. If it does what you expect, your release will too.
The full details are in the SDK docs, under Dev install.