Managing Projects

Your project hub is the home base for all your apps. Here's everything you need to know about keeping things organized.

---

The project hub

When you open Vulcan, you land on the project hub — a list of all your apps. From here you can:

• Open any project to continue working on it
• Search for a project by name
• Star projects to keep favorites at the top
• Create a new project
• Delete projects you no longer need

---

Creating a project

Click New App and describe what you want to build. Optionally pick a template. That's it — Vulcan creates the project and drops you straight into the chat.

Your project is immediately saved and accessible from the hub.

---

Renaming a project

Inside a project, you can update its name and description from the project settings. Pick names that make it easy to find later — something like "Driver Stop Tracker" or "Ops Dispatch Board" is much more useful than "My App 3."

---

Standing instructions

You can give the AI a persistent set of instructions that apply to every chat turn in this project. These are injected as an additional system instruction on every message — the AI always has them in view without you needing to repeat yourself each session.

Click the gear icon (⚙) in the IDE header → scroll to Standing Instructions below the API key section → type your instructions → click Save instructions. Up to 2000 characters.

Good uses for standing instructions:

• Enforcing project conventions ("Always use the Veho navy blue color scheme — never introduce new colors")
• Protecting parts of the app ("Never touch the authentication middleware unless I specifically ask")
• Defining output style ("All date fields should display in MM/DD/YYYY format")
• Encoding domain knowledge ("This app is used by ops managers, not engineers — keep the UI simple and avoid technical jargon")

Standing instructions are per-project and only visible to the owner and editors. See The App Builder → Settings for full details.

---

Starring / favorites

Click the star icon on any project card to pin it to the top of your hub. Handy if you have a lot of projects and a few you return to constantly.

---

Deleting a project

You can delete a project from the project hub or from inside the project settings. Deleting a project removes:

• All its code and files
• Its chat history
• Its preview and production deployments
• Any storage (KV, database, or file bucket) provisioned for it
• All saved versions

This is permanent. There's no undo, so be sure before you delete.

---

Taking your code outside Vulcan

Your app's code is a standard Cloudflare Worker — TypeScript compiled with esbuild, structured exactly like any Workers project you'd find on Cloudflare's docs. You can read it, understand it, and learn from it.

However, running it outside Vulcan is not a simple copy-and-deploy. A few things are tightly coupled to the platform:

• Resource IDs — the wrangler.toml references specific KV, D1, and R2 resource IDs provisioned under the Veho Cloudflare account. You'd need to provision new ones and update the file.
• SQL migrations — Vulcan's deployment pipeline applies .sql migration files automatically. Outside Vulcan, you'd run these manually with wrangler d1 migrations apply.
• Secrets — all secrets are stored against the Vulcan-managed Worker. You'd need to re-enter them on a new deployment.
• Authentication — the Cf-Access-Jwt-Assertion header your app reads is injected by the Nyx gateway after verifying the user's Vulcan session. On a standalone deployment outside Nyx, getUser() would return anonymous for everyone.
• Cron jobs — job scheduling is managed by the Vulcan platform. The VULCAN_CRON_SECRET and cron dispatch infrastructure don't travel with the code.
• URL routing — apps are served under a subpath (/yourname/appname/). A standalone deployment would need its own routing.

The code is yours to read and reference. Fully porting it to run standalone outside Veho's infrastructure is possible but requires significant rework of the above. If you need to do this, contact the platform team.

---

Sharing a project

Every project supports team collaboration. As the owner, you can invite any Veho employee to join your project and give them an editor or viewer role.

Roles

Role	Can chat with AI	Can deploy to production	Can view files	Can manage team
Owner	✓	✓	✓	✓
Editor	✓	—	✓	—
Viewer	—	—	✓	—

Note: Editors can chat with the AI and trigger preview deploys but cannot promote to production. Only the project owner can push a production release.

Inviting someone

1. Open your project in the IDE
2. Click the Team button in the top-right header
3. Choose a role (Editor or Viewer) and click Generate Link — the invite URL appears in a text box and is copied to your clipboard automatically
4. Send the link to your teammate — the link is single-use and expires after 48 hours

When they open the link, they'll be added to the project and redirected straight into the IDE.

Managing your team

From the Team panel you can:

• See all current members and their roles
• Change a member's role with the dropdown
• Remove a member from the project

Team activity feed

Click Activity in the chat panel header to see what your teammates have been building. The feed shows all members' completed turns — who sent the message, when, a summary of what they asked, and a summary of Vulcan's response. It's a shared read-only log; everyone's personal chat thread stays private. Capped at the 100 most recent turns across all members.

This is useful when you open a project after a teammate has been working in it — you can quickly catch up on what changed and why before asking Vulcan to make more changes.

A note on concurrent editing

Only one AI session can run at a time per project — if a teammate is currently chatting with the AI, you'll see a "request already in progress" message and need to wait a moment. File reads and the preview are always accessible regardless.

Sharing the live app

You can share the preview or production URL with anyone at Veho — all Vulcan apps require a Vulcan login, so only logged-in Veho employees can open them. This is separate from project collaboration: sharing the URL lets people use the app, not edit it in the builder.

---

Limits

What	Limit	What happens if you hit it
Apps per user	10	You'll see an error when trying to create a new app. Delete an old one first, or contact the platform team to increase your limit.
Storage per user (across all projects)	100 MB	New writes will fail. Delete unused data or old projects to free space.
Individual stored value size	25 MB	Values larger than this can't be saved. The AI will handle this constraint automatically.
Total project file size	~25 MB	Very large projects may hit build limits. Usually only a concern if the AI has generated a huge amount of code over many sessions.
Concurrent chat sessions	3	You'll see a "maximum concurrent sessions" message. Wait for one to finish before starting another.
Background job run time	30 seconds per job	Jobs that exceed 30 seconds are automatically retried up to 3 times. If all retries fail, the job is dropped until the next scheduled tick. Ask the AI to break long-running jobs into smaller steps or reduce the work done per run.
Chat message length	50,000 characters	The message won't send. Shorten it or split it into multiple messages.

If you need a limit increased, reach out in #eng_product_platform_team.