Skip to content

Incomplete information

This page stores short, user-useful notes that are not complete enough yet for their own full guide section.

Some project root and local file operations rely on the File System Access API.

  • Use modern Chromium-based browsers for the best experience.
  • In older browsers, behavior can fall back to additional permission prompts.

The first folder picker may only show the chosen folder name. If that happens, use the access prompt to grant Aisman permission to the actual project folder.

The settings area includes local/template comparison workflows for instruction files.

  • This area supports preview-first workflows.
  • Detailed merge and conflict resolution behavior may evolve further.
  • The comparison view uses Latest/Previous/Local columns with pair-based comparison and difference navigation.

Issue detail and AI session detail areas include advanced interaction modes that may continue to evolve:

  • Classic vs continuous tab viewing modes.
  • Lazy loading per tab/section to reduce repeat server calls.
  • Hierarchical parent display and quick navigation between related items.
  • List reorder tools (drag/drop and move actions) with persisted ordering.

If a specific control behaves differently between tabs, treat the current UI behavior as authoritative until this guide is expanded with dedicated walkthrough pages.

Additional output-processing behaviors are available but not yet fully documented end-to-end:

  • Running-state rows for files still being written by an AI agent.
  • Assisted Fix dialog with inline re-check and content editing.
  • Preview-oriented output viewer improvements (line context and counters).
  • Auto-processing order rules when earlier files are blocked.

Use the Output processing reference page for baseline behavior and treat UI labels/actions as authoritative for edge cases.

Session issue filtering and ownership modes

Section titled “Session issue filtering and ownership modes”

AI Sessions and Issues include advanced filtering/ownership capabilities that may evolve further:

  • Filter-to-session workflows between AI Sessions and Issues.
  • Additional toolbars for status/type/session filtering.
  • Cross-user ownership/assignment views in organization contexts.

If a team relies on these advanced modes daily, create a local team guide until this section is expanded with full walkthroughs.

Story grouping and move workflows are available, but some edge-case behavior can still evolve:

  • Rearrangement guidance messages in complex move sequences may vary by current list state.
  • Epic edit and delete flows can differ depending on whether stories are still active or already executed.
  • Group visibility can depend on active, executed, and empty-epic conditions.

Treat on-screen dialog text and button states as authoritative when these edge cases appear.

Use the dedicated Pricing and subscriptions guide for current administrator and end-user billing workflows.

Remaining edge-case and rollout differences can still appear between environments, so treat the currently visible UI labels and actions as authoritative when behavior differs from older screenshots.

Home-page legal/compliance behavior is available but does not yet have a full walkthrough page.

  • The cookie consent prompt is shown on the home page and only when Aisman detects a likely GDPR-style locale.
  • The prompt distinguishes essential cookies from optional preference cookies.
  • Footer links provide the current Privacy Policy, Cookie Policy, and Terms pages.
  • The choice is remembered locally so returning users do not have to answer it again on every visit.

If a search is already represented in the current result list, Aisman can reopen that existing subsection instead of adding a duplicate entry.

  • Existing result groups can be expanded again.
  • Matching content can be highlighted in place.
  • Visible headers may be scrolled back into view automatically.

Workflow process-output advanced monitoring

Section titled “Workflow process-output advanced monitoring”

Workflow Step 4 monitoring includes live file detection, validation states, and guided fix actions.

  • Multi-task process-output views can present different visual states depending on how many active loops are running.
  • Backdrop/progress visualization and update notifications may continue to receive UX refinements.
  • Some restart edge cases (for files moved while a tracker was paused) can still show partial state and are being refined.

When in doubt, use the current checklist state and validation buttons shown in the UI as the source of truth.

Recent-item lists (Latest issues, Latest sessions, Latest stories) and workflow reload restoration behavior are available but still evolving in edge cases.

  • Section collapse defaults and animated reordering can vary by current page context.
  • Cross-device synchronization timing may differ from local instant updates.

Rely on visible list order and current badges as the immediate source of truth.