FAQ

What does Forge generate today?

Forge currently ships one active artifact type: itk-batch.

Supported patterns:

• file-input-mutate
• query-export
• query-update
• simple-operation

Does Forge run code against Teamcenter?

No. Forge generates source artifacts and build scripts. Build, deployment, and execution happen in the customer environment.

Which Teamcenter versions does Forge target?

The request payload requires a tcVersion, and that context is passed into generation. Forge does not claim universal compatibility across Teamcenter releases. Teams should validate generated output against their exact Teamcenter environment, SDK, and compiler toolchain.

How is generated output checked?

Forge applies scaffold and code validation before returning files. Diagnostics are returned with generation results so engineers can review issues before using the output.

Is the knowledge base exposed to users?

No. The knowledge base is server-side generation context. It is not shipped as a client-facing product artifact.

How do I authenticate?

• Web app: magic-link session
• Integrations: Bearer API key

Is the CLI available now?

Not as a public self-serve product surface.

This repo does include a CLI implementation with:

• forge init
• forge login
• forge logout
• forge whoami
• forge generate

That CLI is currently repo-local for development and internal evaluation. It scaffolds projects locally and sends authenticated generation requests to the Forge API. It does not run the generation engine on the local machine.

Why do some schemas mention artifact types I cannot generate?

The API contract reserves additional artifact ids for forward compatibility. The default registry in this repo currently exposes only itk-batch.