Skip to main content

Make a change without writing code

You can change your product without writing code. Describe the change in a chat session, check it in the Preview, and press Open PR. Your engineers review and merge the pull request as usual.

Before you start​

  • Ask a workspace admin to invite you. See Members and roles.
  • Make sure the project is imported and deployed. An engineer usually does this once, and sessions cannot start before the first deploy finishes. See Deploy your project.
  • Open Settings > Your Account > Preferences and choose Not-tech beside Agent replies. The agent then talks to you without technical terms.
  • If you want the pull request under your own name, press Connect beside GitHub in Settings > Your Account > Account.

Describe the change​

  1. Open the project and press New Session.
  2. Describe what you want in your own words. "Swap the headline on the pricing page and reword the plan cards" is enough.
  3. Attach a screenshot if a picture says it better. You can add up to 10 files of up to 10 MB each.
  4. Press Start session.

The agent works on its own copy of your product, on a new branch. You can keep typing while it works. Your message waits in Up next and goes as soon as the agent finishes. When the agent needs a decision, it asks you a question in the chat. Pick an answer, or type your own, and press Submit answers.

Check it in the Preview​

Open the Preview tab. It shows your product running with the change. Click through it and try the case you had in mind.

If something looks wrong, say what you see, for example "the button overlaps the text on a phone". The agent fixes it in the same session, and the Preview updates. Preview and sandboxes covers the Preview's tools.

Ask for a mockup or a write-up​

Before a change is built, you can ask to see it. Try "show me a mockup of the new plan cards" or "write up how the checkout emails work today".

The agent answers with an artifact, a document or a mockup you read in the Artifacts tab. Artifacts stay with the session and never go into the pull request. See Artifacts.

Open the pull request​

When the Preview looks right, press Open PR. The agent commits its work, pushes the branch and opens a pull request on your repository, ready for review. The session moves to Under Review. The chat shows a Ready for review banner with a Resume button. A message you send also takes the session back to Active.

With a GitHub Connection, the pull request opens under your GitHub account. Without one, it opens as Kosuke App.

What your engineers do next​

Your engineers review the pull request on GitHub and merge it as usual. When it merges, the session moves to Completed. If they close it instead, the session moves to Archived.

If they ask for changes, press Resume in the chat. The session goes back to Active, and you can ask the agent for the changes. Open a pull request explains what happens on GitHub.

Next steps​