dreamagent_create_project
WRITE ACTION — creates a new DreamAgent project (website, Telegram bot, Discord bot, or scheduler). Use ONLY when the user clearly asks to create/build a new project; not for questions about what to build.
CONFIRM BEFORE CALLING — never create on the first mention. In ONE message, present and get the user's explicit go-ahead for:
The credential: run dreamagent_list_global_integrations first. If several telegram/discord credentials are saved, list them (id + title) and ask which to use. If exactly one is saved, state which one you will use. Never pick silently.
The plan: name, type, and the final description exactly as you will submit it (this is the Prompt Assistant's recommendation summary). Call this tool only after the user confirms.
CREATION IS ASYNCHRONOUS: after calling, check dreamagent_get_project_status repeatedly until the project is 'ready' or 'failed' (bots ~2-5 min, websites longer).
CREDENTIALS: raw bot tokens are never accepted in chat or as inputs. For Telegram/Discord bots you MUST pass bot_token_integration_id — the ID of a saved credential from dreamagent_list_global_integrations. If none is saved, direct the user to dreamagent.cloud → Settings → Global Integrations. Other saved keys can be imported via global_integration_ids. Credentials are stored as project secrets and are never exposed back.
DESCRIPTION = the refined creation brief. Act as a Creative Director / Product Manager, not an architect.
Create a concise but complete description of WHAT should be built:
product vision and target audience
user experience and core functionality
design/tone direction
important features and behavior
final expected result
Do not include implementation details such as:
technology stack
architecture
database/API implementation
authentication implementation
deployment
CI/CD
testing commands
Infer reasonable defaults when missing details are non-critical. Ask for clarification only when missing information materially affects the requested functionality, scope, credentials, or expected result.
Prefer the following structure and constraints for each project type, but do not override explicit user requirements:
Website:
Project Vision
Design Style
Pages
Hero Experience
Core Features
UI Components
Mobile Experience
Final Expectation
Prefer up to 4 pages unless the user clearly requires more.
Telegram bot:
Bot Purpose
Commands
User Flow
Optional AI Features
Integrations when required
Final Expectations
Prefer a compact command set; always include /start and /help unless the user's explicit requirements conflict.
Discord bot:
Bot Purpose
Slash Commands
Events
Permissions
Optional AI Features
Final Expectations
Prefer a compact command set; include /help where appropriate.
Scheduler:
Job Purpose
Data Sources
Schedule
Delivery Channels
Message Format
Final Expectations
Use concrete schedules and specify failure/timeout behavior.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | project name (max 30 chars; a public subdomain is auto-generated). | |
| env_vars | No | optional non-secret environment variables. | |
| description | No | the build request (what + for whom + features/tone). | |
| project_type | Yes | website / telegrambot / discordbot / scheduler. | |
| global_integration_ids | No | optional saved-key IDs to import as env vars. | |
| bot_token_integration_id | No | REQUIRED for telegrambot & discordbot — saved-credential ID (see dreamagent_list_global_integrations). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |