Skip to content

Guides

Each guide answers one specific question.

Setup

  • Configure the conception path — change the folder condash renders, with the menu, the CLI, or by editing settings.json.
  • Repositories and open-with launchers — the workspace and worktrees paths, the repositories list, and the IDE/terminal launch slots behind the Code pane.
  • The Settings modal — one scrolling modal, two files with disjoint schemas, and which setting lives where.
  • Applications and handles — identify each app by one canonical #handle, manage the registry, keep apps: references resolving.
  • Auto-commit — let condash be the single writer for a versioned conception: commit settled changes on a timer and push.

The panes

The activity rail has three separated groups: Projects, the four working panes (Code, Knowledge, Resources, Skills), and Terminal. Clicking an active button hides its pane; clicking an inactive working button selects it without changing Projects visibility. Hidden state persists across restarts, including empty and terminal-only layouts. The View menu shows working panes without toggling them and retains the Terminal toggle. Automations, Logs, and Diagnostics remain labelled top-bar full-window overlays, not rail or native View routes.

  • The Projects pane — the status stack, changing status, creating items, closing and reopening.
  • The Code pane — what the repo cards, branch rows, and worktrees mean.
  • Automations (tasks) — save reusable, parameterized agent prompts, fill their {markers} in a form, and run them with one click.
  • The knowledge tree — durable reference material as cards, with freshness stamps.
  • The Resources pane — every file under resources/ as a card with view / open / copy / paste-to-term actions.
  • The Skills pane — browse the markdown skills condash ships under .agents/skills/, with shipped/diverged chips.
  • The Logs pane — saved session transcripts by day, a virtualised viewer with search, and the task-run store.
  • Retired Deliverables pane — historical description of the removed aggregate; item-level deliverables remain available from project previews.
  • Terminal diagnostics — per-tab memory, growth rate, and throttle state, plus main-process event-loop delay.

Daily

Extending

  • Management skills — the five shipped skills as slash commands: which one to pick for a task, and what each wraps in the CLI.
  • Extend the management skills — fork or wrap the five shipped skills without losing upstream updates.
  • Dev launch — run condash from a clone with hot reload, and the test targets that guard it.

More

→ Looking up rather than doing? Reference.