Skip to main content

Create your first chat

This walkthrough takes you from a blank homepage to a set of tasks ready to ship. The whole flow is a conversation — you bring the intent, Rezonant brings the structure.

1. Start from the homepage​

The homepage asks one question: "What are you working on?" Pick the entry point that matches where you are:

  • Idea — "I have an idea I want to explore." Best when you're starting from a thought rather than a document.
  • Document — "Here's a document I'd like to turn into actionable tasks." Drop in a PRD, a spec, or notes you already have.
  • Nothing — "I'm not sure what I want to build yet." Use this when you want to think out loud and let the conversation find the shape.

If you'd rather start from a specific goal, the quick-action pills give you a running start: Analyze User Friction, Draft PRD, Draft Spec, Plan Integration, Explain Feature, Break Down Tasks, and Investigate Bug.

2. Talk it through in the chat​

Once you're in, you're in the chat view — an interactive conversation thread. The agent gathers context from your codebase, connected repositories, and existing tickets, then asks clarifying questions to sharpen the intent. Answer in your own words. The more clarity you bring here, the better the structure that comes out.

3. Review the proposed task structure​

When the agent has enough to work with, it proposes a ticket structure — a hierarchical view of the tasks it intends to create, each with a type, tags, and a short summary. The structure sits in an "awaiting structure confirmation" state so you can read it over before anything is committed.

Take a moment to check the shape: are these the right pieces of work, broken down the way you'd break them down?

4. Confirm and refine​

Confirm the structure to move into the ticket view, where each task appears as a card. Open any card to reach the ticket detail view for a single task, where you can:

  • edit the title and description,
  • assign tags (Coding, Design, Research, Documentation, Testing, Agent),
  • attach documents and images, and
  • connect the task to external systems.

This is where you turn a rough structure into work that's genuinely ready to hand off.

5. Ship it​

From a task you can:

  • Push to Linear or Jira to land it in your team's tracker.
  • Assign it to a team member to pick up.
  • Send it for autonomous coding by applying the Agent tag, which hands the task to a coding agent to execute.

That's the full loop: capture the intent, give it structure, refine it together, and move it toward shipped code.

Keep going​

  • Integrations — connect the tools your tasks come from and go to.