Docs
Start for free

Use a Project

Create a Project, add the files a task needs, generate a result, then review and organize the work in one place.

A Project is the workspace for one piece of work. Keep its source files, task instructions, and generated results together so you can review or continue the work later.

Use a Project when a task depends on files, needs several rounds of revision, or may be handed to someone else. A quick question that does not depend on saved context can stay in Chat.

What a Project keeps

  • Source files: the documents, PDFs, spreadsheets, folders, images, or other references used by the task.
  • Task context: the conversation and instructions that explain what to produce.
  • Results: the files Kuse creates from those sources and instructions.

Build each Project around one outcome, such as “Q3 operations report” or “New client onboarding”. Start a separate Project when the client, reporting period, audience, source set, or final deliverable changes.

Kuse does not automatically use files or the complete conversation history from another Project as source material. Select the required files or connected-service content for the current task. Account-level memory depends on current product settings and does not replace the source files the task needs.

1. Create and name the Project

  1. Open Projects and create a Project.
  2. Name it after the outcome, client, or period. Replace names such as “New Project” before the work grows.
  3. Keep unrelated clients, periods, and deliverables in separate Projects.

A shallow structure is enough for most work. Keep a small task at the Project root. When the file set grows, add folders such as Source files, Reference, and Produced files. A Note can hold a short brief, a decision, or context that should stay with the work.

2. Add the files the task needs

Start with a focused source set:

  • Files that contain the facts Kuse must use.
  • A file that defines the required structure, if one exists.
  • One useful example when the result should follow an existing pattern.

Use file upload for a small selected set. Use folder upload when the folder structure explains the source groups. Remove duplicates and outdated versions, use clear file names, and confirm that important files open correctly before starting the task. Do not use real confidential data in a public demo.

If an upload fails, confirm that the file is supported, readable, not password-protected, and within any size limit shown in the interface. See Supported file types for format details.

3. Describe the task

A useful request answers five questions:

  • Sources: Which files should Kuse use?
  • Outcome: What file or result should it create?
  • Structure: Which sections, columns, order, or format are required?
  • Audience and use: Who will read it, and what happens next?
  • Evidence rules: How should missing, conflicting, or unsupported information be handled?
Use the selected source files to create a spreadsheet-ready reconciliation table. Include source file, account name, currency, date, description, income, expense, closing balance, and status. Normalize dates and amounts. If a value is not supported by the source files, leave it blank and mark the status as "To confirm".

If a reference file controls the layout but should not be treated as factual evidence, say so. Ask Kuse to show conflicts and mark missing information instead of guessing.

4. Open and review the result

Generated files stay in the Project with the sources and conversation that produced them. Open the result and check:

  • Every requested section, column, or output element is present.
  • Names, dates, totals, and source references match the original files.
  • Missing information and conflicts are visible.
  • The format works for the intended reader and next step.

Preview, editing, sharing, and download actions vary by file type. Use the actions shown for the current file. If something is wrong, ask for one specific revision in the same Project, such as adding a missing column or preserving source names. Download the file when the next step happens in another tool, then open the downloaded copy once before delivery.

5. Keep the Project easy to use

  • Use folders for real groups, not every small difference.
  • Rename files with a purpose, period, or review state. Avoid names such as final2 or final-new.
  • Move files when their current location hides the relationship between sources and results.
  • Use the available Download, Share, Move, and Trash actions for the selected item. Check Trash before assuming an item is permanently gone.
  • Pin active Projects, then use search or Recents to return to older work. Files shared with your account appear under Shared with me.

The upload menu can also accept a YouTube link. Kuse currently relies on videos with readable subtitles for analysis, so confirm the subtitles before treating the video as a required source.

Before you hand off the result

  • The Project name and file names make the work understandable without guesswork.
  • The source set contains the evidence needed for the result.
  • Important claims, values, and references have been checked.
  • Missing information is marked clearly.
  • The final file opens in the place where it will be used.

Open Projects