TrigCode AI
    TemplatesShowcasePricing
    Help center

    Getting started

    Welcome to TrigCodeBuild your first appChoose an app typeWrite effective promptsNavigate the TrigCode workspace

    Building and editing

    Understand the build lifecycleEdit an app with conversationPreview and test your appWork with code and filesUse checkpoints and rollbackOrganize work with projects and templatesUse reference images and app secrets

    Export and deploy

    Export source codeConnect GitHub, GitLab, or BitbucketDeploy on TrigCodeDeploy to external providersPreview mobile apps and build an APKConnect a custom domain

    Plans, credits, and account

    Plans and feature accessCredits and action costsBilling, renewals, and plan changesAccount and security settings

    Teams and enterprise

    Teams workspacesRoles, budgets, and governanceConfigure SSO and SCIMShared prompts, usage, and audit history

    API and automation

    API authentication and scopesAPI task referenceAPI organization resource referenceReceive signed webhooks

    Troubleshooting

    Troubleshoot builds and editsTroubleshoot previewsTroubleshoot deployments and domainsTroubleshoot billing and creditsGet support
    Help/Building and editing/Edit an app with conversation

    Building and editing

    Edit an app with conversation

    5 min readReviewed 9 September 2026

    Make controlled follow-up changes while preserving the working project.

    On this pageHow conversational edits workA useful edit requestEdit credit cost

    How conversational edits work

    Eligible plans can continue the same task after the first build. The agent receives a compact view of the current project and recent conversation, loads relevant files, applies changes, validates the current revision, and creates a new checkpoint.

    1. Test the current behavior and describe one coherent change.
    2. Include the expected result and anything that must stay unchanged.
    3. Wait for the edit to reach a terminal state.
    4. Refresh and test the affected flow in preview.
    5. Use version history if the change is worse than the prior revision.

    A useful edit request

    Exampletext
    On the invoice editor, changing quantity updates the row total but not the subtotal. Fix that calculation, keep the current layout, and verify the empty and zero-quantity states. Do not change the invoice PDF styling.

    Edit credit cost

    A follow-up edit starts at 15 credits. A selected premium model can apply the same model multiplier used for builds. Auto routing is the best-value path because it stays at the base credit rate.

    Still need help?Open a support ticket from your workspace or contact the TrigCode team.
    Contact support

    Related guides

    Write effective promptsGive the build agent enough product and design context without creating a brittle mega-spec.Work with code and filesBrowse generated files, make careful manual edits, and understand plan gates.Use checkpoints and rollbackUnderstand automatic versions, manual checkpoints, and safe restoration.
    PreviousUnderstand the build lifecycleNextPreview and test your app

    On this page

    How conversational edits workA useful edit requestEdit credit cost
    TrigCode AI

    Bring your ideas to life with AI.
    Build, refine, and make them yours.

    Start building

    Product

    • AI app builder
    • Templates
    • Showcase
    • Pricing
    • Teams & enterprise

    Build

    • Websites
    • Web apps
    • Mobile apps
    • Games
    • Dashboards
    • CRM
    • SaaS
    • Scheduling
    • AI assistants

    Resources

    • Help center
    • Building guides
    • Compare builders
    • Vibe coding explained
    • What you can build

    Company

    • About TrigCode
    • Contact us
    • Trust & security
    • Get support

    © 2026 THS CyberSecure Private Limited.All rights reserved.

    Privacy policyTerms of service