Skip to content
Aisman Docs

Quick start

This guide walks you through the first steps needed to start using Aisman.

0. Confirm your account first

Section titled “0. Confirm your account first”

If your workspace enforces email confirmation, complete the email-confirm flow before your first sign-in.

  1. Sign in with your account.
  2. If confirmation is required, open the link from your email.
  3. If you did not receive the email, use the resend option on the check-email screen.

After confirmation, return to sign-in and continue normally.

1. Create a project

Section titled “1. Create a project”

From the dashboard, open Projects and choose New project.

  1. Enter the project name and optional description.
  2. Set the project root folder using Browse or drag-and-drop.
  3. Confirm the folder exists on the current machine and keep the full path handy if the browser only shows the folder name.
  4. Save only after root access is granted.

If root path or access is missing, Aisman blocks project workflow actions until you fix it.

2. Grant root folder access

Section titled “2. Grant root folder access”

When prompted, grant directory access so Aisman can read and write .aisman exchange files.

  • Aisman can guide you to the right control and prompt you to grant access.
  • The app uses the browser’s file access features, so the folder picker and the access prompt may happen in two separate steps.
  • Access state is remembered per machine and project.
  • You can remove granted folder permissions later and re-grant when needed.

3. Run your first AI cycle

Section titled “3. Run your first AI cycle”
  1. Generate a prompt from Aisman.
  2. Run the coding agent.
  3. Return to Aisman and open New detected AI outputs.
  4. Review files and process all or selected outputs.

If unprocessed outputs exist, Aisman keeps focus on output handling before normal flow continues.

During processing, Aisman shows a full-page progress overlay and updates the message in real time (file name first, then per-issue progress when needed).

If a newly detected file is still being written by the AI agent, the Actions column shows a Running state instead of action buttons until the file is ready for validation/processing.

If only part of a batch succeeds, processed files are archived while failed files stay in New detected AI outputs for correction and retry.

When a file needs fixing, use the built-in Fix flow to re-check the same file after edits instead of restarting the whole batch.

4. Select the right workspace context

Section titled “4. Select the right workspace context”

Before creating or reviewing projects, make sure you are in the expected workspace context:

  • Personal workspace
  • One of your active organizations

This selection controls which project list and session data are shown in the dashboard.

If you start a session directly in the coding agent, Aisman can still pick up the output files later as long as the project’s .aisman folder is available.

5. Track AI cost quickly

Section titled “5. Track AI cost quickly”

After your project is active, you can monitor AI usage cost from detail tabs:

  • Project -> AI cost: total project AI cost plus breakdowns by user, agent, and tool.
  • Organization -> AI cost: summed organization cost with per-project and aggregate breakdowns.

Use this view to spot unusually expensive processing runs and decide whether to optimize prompts, issue batching, or model choices.

What’s next?

Section titled “What’s next?”