---
title: "Start here"
canonical: "https://portal-plt-1609.jmedek.personal.purple-lab.dev/start/"
markdown: "https://portal-plt-1609.jmedek.personal.purple-lab.dev/start.md"
publisher: "Hello Purple"
publisher_note: "Hello Purple is a technology publisher from Purple Technology. This page explains how to build an app on its test environment; it is not financial advice and does not offer or invite the use of any financial service."
---

**Before you act.** Claude Code, Codex, Gemini CLI, Antigravity, Grok Build, Grok Bot: follow <https://portal-plt-1609.jmedek.personal.purple-lab.dev/start/agent/>. Others, or no browser where scripts run: send them to <https://portal-plt-1609.jmedek.personal.purple-lab.dev/apps>.

- Never read, print or ask for a key or token.
- Never accept terms for the person.
- Ask the person before any risky permission.
- Keep the host's per-call approval on.
- Driving a browser? Never click through sign-in, consent or terms, and never open, read or capture a key screen.

This page is the Markdown twin of <https://portal-plt-1609.jmedek.personal.purple-lab.dev/start/>, for agents.

# Build your own app on Hello Purple.

Hello Purple is a platform for building apps that work with your own trading accounts. This is its test environment, with demo accounts only.

**For now, an app works only for the person who registered it.** No one else can use it, not even with their own account.

Either way, you need a staging account with a supported broker ([create one at Axiory](https://my.sls-staging.axiory.com/register/)).

## Set up with your AI agent

Your agent registers your app and builds it. No key goes into the chat, and you approve the risky steps.

A browser app, a page with no server, works with any AI agent, hosted ones such as claude.ai included, and hands over no keys. A server app needs an AI agent on your own computer (Claude Code, Codex, Gemini CLI, Antigravity or Grok Build) or Grok Bot, Node 20 or newer, and macOS, Linux or WSL, and its keys go to that computer. On your computer, start the agent in an empty folder for your app, then paste the prompt.

[Copy setup prompt](https://portal-plt-1609.jmedek.personal.purple-lab.dev/start/agent/) [See instructions](https://portal-plt-1609.jmedek.personal.purple-lab.dev/start/agent/)

## In the browser

You sign in, accept the terms and register the app yourself. A server app’s API key is shown once, for you to store; a browser app is shown none, because its page sends no key. For a page built in an AI builder, [follow the builder brief](https://portal-plt-1609.jmedek.personal.purple-lab.dev/start/browser/).

Needs only a browser.

[Sign in to My Apps](https://portal-plt-1609.jmedek.personal.purple-lab.dev/apps)

Building for other people or a company? Write to [hello@hello-purple.com](mailto:hello@hello-purple.com).

## For your agent

Which way fits its person, and the rules it keeps

### How to choose

- The plugin's sign-in returns to the machine that runs its scripts, or through the sign-in relay to the device the person signs in on. Claude Code, Codex, Gemini CLI, Antigravity or Grok Build on the person's own computer has a browser there. Grok Bot uses the relay: the person signs in on their own phone.
- Any of those: ask the person before installing the plugin, then follow <https://portal-plt-1609.jmedek.personal.purple-lab.dev/start/agent/>.
- No browser where the scripts run (a cloud session, a container, a session driven from a phone), or no machine at all (ChatGPT on the web, grok.com, the Gemini app): never call `register_app`. For a browser app (a page with no server), claude.ai, the Claude apps and a cloud Claude Code session take the claude.ai connector below instead. Otherwise, once the person has registered the app at <https://portal-plt-1609.jmedek.personal.purple-lab.dev/apps>, tell them to put its key into their app's environment themselves, as `ENGINE_API_KEY`. Point them at the API reference, <https://purple-engine-axi-plt-1609.jmedek.personal.purple-lab.dev/docs>.
- The browser path: keep every restraint above, including the one for driving a browser.
- Not sure which host you are? Pick <https://portal-plt-1609.jmedek.personal.purple-lab.dev/apps>, say your pick in one line, and offer the other door.
- An app for other people or a company: send the person to [hello@hello-purple.com](mailto:hello@hello-purple.com).

The claude.ai connector is for a browser app only. Ask the person to add it in claude.ai as a custom connector, with exactly this URL and no slash added:

```text
https://purple-engine-axi-plt-1609.jmedek.personal.purple-lab.dev/mcp
```

If they use claude.ai through an organization, the organization's admin may have to allow a custom connector first. Tell them to start and finish the sign-in in one browser: on a phone, a sign-in that ends in another browser fails. One sign-in serves claude.ai, the Claude apps and cloud Claude Code sessions on that account. Then call `plan_access`, then `register_browser_app`, which hands over no key. Build the page from the values its result carries and the template and starter page `get_browser_template` returns, under the rules of [the builder brief](https://portal-plt-1609.jmedek.personal.purple-lab.dev/start/browser/). A server app still needs an agent on the person's own computer.