Session types

Use this page when you need to choose the right session type before running a workflow cycle.

1. Available session types

Aisman supports four session types:

Normal: Default development workflow sessions.
Documentation: Sessions dedicated to keeping user/help docs updated.
Consolidation: Sessions for collecting unresolved issues from older sessions.
Periodic: Sessions for repeatable tasks that restart in cycles.

2. Creating a special session

When you create a new session, open Session steps and enable special-session mode.

Turn on Make this session a special session type.
Select one of the available special types.
Keep that selection until it is persisted.

After selection, Aisman labels the session with its type in lists and detail views.

3. Documentation sessions

Use a documentation session to generate and process help-source input for docs maintenance.

Use the session description to define where docs live and how they are maintained.
Continue using Workflow steps normally, then process the generated docs output.
You can use more than one documentation session in a project when needed (for example separate tracks or cleanup runs).

Documentation-session behavior highlights:

Session special type is saved immediately when selected.
Step 1 can auto-mark unstarted documentation issues as ready for processing.
Step 2 can continue without selecting a coding issue, but still confirms story text is documentation-only before advancing.
During output import, session name/description values are preserved for documentation sessions.
Help source generation runs in batches and respects a maximum file-size limit.
The maximum help-source size is read from MaxSourceFileSizeKb using your effective per-user setting.
Canceling documentation generation closes the progress popup and cleans up that run’s generated source file.

4. Consolidation sessions

Use consolidation sessions to close out older sessions that only have a few unresolved issues left.

What happens when you add an issue to a consolidation session:

A new copy of the issue is created for the consolidation session.
The original issue is marked as transitioned.
Transition links are created between original and copied issues.
Historical notes remain traceable from the new copy.

In Workflow issue selection, adding issues into a consolidation session shows warnings and add-to-session indicators so you can confirm intent before processing.

5. Periodic sessions

Use periodic sessions for recurring work that repeats in cycles.

Issues in these sessions can be reset for a new cycle.
Restart cycle resets non-cancelled issues back to Not implemented.
Completed periodic sessions stay active unless all remaining issues are cancelled or removed.
Periodic tasks are prevented from being added into non-periodic sessions.
Periodic issue notes are cycle-aware so each run can keep its own note context.

Periodic sessions are designed for repeatable operations, not one-time implementation passes.

6. Visual behavior and badges

Across AI sessions, Issues detail, and Workflow, special sessions can show type badges/icons so you can quickly identify context.

Documentation sessions have dedicated labeling.
Consolidation sessions display consolidation-specific indicators.
Periodic sessions show periodic labeling and restart controls.