projectroom Titan

Build your application. Reuse the foundation.

Connect VS Code to projectroom, the developer platform by CloudQuest Inc., powered by the Titan framework.

Create applications and develop JavaScript, Java and Go modules with platform templates, shared services and AI development guides. Build, sign and deploy through the same Titan workflows used by the CLI and IntelliJ plugin.

What you can do

• Sign in through your browser and open applications available to your account.
• Create modules from platform templates and prepare managed development tools and dependencies.
• Work with your application source using Git and Titan authentication.
• Build, sign and deploy modules, then open the development page and inspect runtime logs.
• Manage application resources, including databases, KV data, files, SMTP settings, parameters and batch runs, according to your permissions.
• Collaborate with AI using the development guides included in your application workspace.

Requirements

• VS Code 1.95 or later.
• A projectroom account and network access for platform operations.
• macOS on Apple silicon, or Windows on x64 / ARM64, for the bundled native tools in this release.
• Docker for local container builds.
• Relevant language extensions for editing features, such as Svelte, Java or Go support. The plugin can guide you through development environment preparation.

Platform operations use Titan sign-in. You do not need a personal AWS account or AWS CLI credentials.

Your first application

1. Open the Titan view in the Activity Bar and choose Sign In. Complete the connection approval in your browser.
2. Choose Create Application, or Open Application to download an existing application.
3. Create a module from a platform template. Application source is organized under your workspace as userId / appId / moduleId.
4. Run Titan: Build & Deploy Module from the Command Palette or use the module actions.
5. Open the module's development page through its Open action. Use Titan: Runtime Logs to inspect execution.

Open the Command Palette and search for Titan to find the available actions. Platform permissions still apply to every operation.

Develop with AI

Open the application's AI development guide before making changes. For example:

Create a projectroom application with a JavaScript UI and a Java API module.

Build and deploy the modules, then show me the development URL.

AI tools work with the same Titan CLI and application guides. They do not require access to your AWS credentials.

Documentation and support

• Platform website
• Installation, IDE tours and development guides
• Shared platform services
• Support: contact@cloudquest.net

License and preview status

This extension is distributed under the projectroom Titan Plugin License, also included in this package as LICENSE.txt. Its source code is not offered under an open-source license.

This is a preview release. Hosted services and cloud resource usage are subject to your account permissions and applicable service terms.

Moving from a private preview

If you have the earlier private extension (titan-internal.titan-vscode), disable it before enabling this Marketplace extension (cloudquest.titan-vscode). Keep your application folders and sign in again in the new extension. Do not run both extensions in the same VS Code window.

Managed Git on Windows

The plugin automatically prepares Git for Windows in the current user's private ~/.titan/toolchains directory when preparing an application. Both x64 and ARM64 use a pinned MinGit release verified by SHA-256. The first preparation requires an HTTPS download (about 40 MB); later runs reuse the installed copy. No system Git installer, administrator privileges or global OS PATH changes are required. Git authentication continues to use the current Titan account and application permissions. The IDE's native Git UI uses the prepared executable; an existing VS Code Git path selection is preserved. If preparation fails, check the Titan output/notification and retry opening the same application. Do not recreate it. The macOS Git path and existing build/sign/deploy paths remain unchanged.