Skip to content
Get Started KurrentDB

Home & projects

Once a team has more than a handful of repos and agents in flight, “here is every session, newest first” stops being the right first screen. Capacitor now opens on a Home page pitched at what needs you right now, and lets you group repos into projects so navigation, sharing, and analytics follow the lines your team actually works along — not just the raw list of GitHub repositories.

Home — what needs me?

Section titled “Home — what needs me?”

https://<your-org>.kcap.ai/ lands on a personalized Home rather than the session list. It reads across the sessions, agents, and work you can see and pulls the actionable things to the top:

  • Needs your attention — hosted agents waiting on a permission answer or input, and flows or sessions that failed and are yours to deal with.
  • Continue working — the threads you were most recently in the middle of, so you can pick back up in one click.
  • Recent outcomes — freshly generated session outcomes across your repos: what just got done, without opening each session.
  • Pending approvals — grouped by kind: project invites and join requests, and curation promotions awaiting a decision.
  • Active lines of work — your own work items that are still open.
  • Knowledge learned — recent facts and curated guidance worth knowing about.

The full session archive hasn’t gone anywhere — it moved to its own /sessions route (the Sessions tab), and Home links straight into it. Home is simply the first thing you see: a triage screen, not a replacement for browsing.

Projects — grouping repos into a line of sight

Section titled “Projects — grouping repos into a line of sight”

A project is a named group of repositories with its own members. Selecting one scopes the whole dashboard — sessions, analytics, work items — to the union of that project’s repos, so “the checkout squad’s work” is one click rather than a mental filter across five repositories. The repository sidebar is project-first: projects group at the top, each collapsible, and your choice persists across visits.

Each project has an Overview tab showing its repositories, its members (including any team rows), and — for owners and admins — the join requests and invites waiting on a decision. Project owners add members directly; there’s no invite-and-accept round trip for someone already in your organization.

A project is also a sharing principal in its own right. Sessions can be shared to a project, and a new project visibility level sits on the ladder between private and org-wide:

private  <  project  <  org_public  <  public

A session set to project visibility is visible to the members of the project(s) its repo belongs to, and no wider. See Visibility & sharing for the full ladder.

From the CLI

Section titled “From the CLI”

You mostly live in projects from the dashboard, but two read commands surface them in the terminal:

Terminal window
kcap projects              # table: slug, name, repo count, member count, your role
kcap project <slug>        # detail: metadata, repos, members, and (owners/admins) pending requests

your role is one of owner / member / pending invite / pending request / —. Both commands require the Team or Enterprise plan and return a 403 on Free.

To make new sessions default to project visibility, set it once — via the setup wizard, the --default-visibility flag, or:

Terminal window
kcap config set default_visibility project
Section titled “Related”