Starko

A project holds the tickets,the repo and what Starko knows.

Projects group tickets into the work you plan and track. Link one to a GitHub repository and its tickets know where Starko AI should fix them, with a map of the codebase every run starts from.

v2.starko.one/dashboard/projects
Projects
72%
Group Status Filter:All tenantsAll companiesAll clients Search projects
In Progress3 Create project
๐Ÿ›’Checkout redesign12/19Mia Novak
๐ŸงพInvoices and VAT7/15Jon Reyes
๐Ÿ“ฑMobile onboarding3/11Sara Lind
Open2 Create project
๐Ÿ”ŒNorthwind API v20/8Leo Brandt
๐Ÿ“ŒProject brief: partner portal2/6
Backlog2 Create project
๐ŸงชBug bash, November0/9Ana Kovaฤ
๐ŸŒWebsite redesign0/12
At a glance

Projects in short.

Group by
Status, priority, lead or none. Drag a project between groups to change it.
Filter by customer
Tenant, company and client, narrowing from the top down.
Repository
Admins and owners link a GitHub repository. Members see it as a read-only label.
Pins
Per member. A newly set lead gets the project pinned to their sidebar.
Templates
Five starter templates, your own, and public ones. Up to 50 tickets each.
Project context
Six sections and a summary of up to 1,500 characters, flagged for a refresh after a month.
Sharing
Admins and owners turn on a share link. The client signs in with a one-time email code.
Deleting
Admins and owners only. It removes the project and all of its tickets.
Projects list

Every project on one page, grouped the way you plan.

The Projects page lists every project in collapsible groups. Each row shows the priority, the project's icon and name, a progress ring with closed tickets out of the total, the lead and a pin. Group by status, priority or lead, and drag a row into another group to change that value. Search by name narrows what is shown without changing the groups or their counts.
  • Statuses for projects are Backlog, Open, In Progress and Closed. Priorities are Urgent, High, Medium and Low.
  • Filter by tenant, company and client. Picking a tenant narrows the company list, and a company narrows the clients.
  • Each group has its own Create project button, which starts the new project with that group's status, priority or lead.
  • The list refreshes on its own every 30 seconds, and pauses while you drag.
Project page

Tickets in front, context one tab away.

Opening a project shows its tickets with the same views as the main Tickets page: board, list, table and Gantt, saved views and filters. The Context tab slides in as a sheet over the board, so the work you were scanning stays put. It holds the project's properties, a progress bar and a brief you write like a document, with @mentions for teammates.
  • Properties sit as one row of pills: status, priority, lead, team, members, start date, deadline, repository and the linked tenant, company and client.
  • Progress shows Work items closed out of total, plus Unassigned, No deadline and Past due counts.
  • Picking a team limits the lead and members to that team's roster.
  • Presence avatars show who else has the project open. Tickets open in a side sheet, so you never lose your place.
  • The โ‹ฎ menu pins or unpins the project, saves it as a template, shares it, stops customer emails or deletes it.
v2.starko.one/dashboard/projects/8c1eโ€ฆ?context=1
Projects/๐Ÿ›’ Checkout redesign
72%
Tickets Context
Open
high

Coupon field hides the order total on mobile

medium

Remember the last used payment method

In Progress
urgent

Address form loses focus after autocomplete

Closed
medium

Show VAT on the review step

Context
๐Ÿ›’

Checkout redesign

A shorter checkout for mobile buyers: fewer fields, clearer totals.

In Progress High Mia Novak Web teamMembers Nov 3, 2026 Dec 12, 2026 northwind/web-appNorthwind
Progress63%

12/19

Work items

2

Unassigned

5

No deadline

1

Past due

Goal

Cut checkout from five steps to three. Mobile buyers drop off at the address step, so autocomplete and a single review page come first.

Out of scope

New payment providers. Guest accounts stay as they are.

Unpin from sidebar
Save as template
Stop emailing the customer
Share
Delete project
Repository

Link a GitHub repository, and every ticket knows where to be fixed.

A project's Repository field points at one of the repositories the Starko GitHub App can access. Once it is set, every ticket in the project dispatches Starko AI into that repository, and the ticket views show each ticket's pull request state. The gear next to the repository opens the project's Starko AI settings: agent instructions, sandbox commands, encrypted environment variables and auto-dispatch.
  • When someone mentions @starko, the repository is resolved in order: the ticket's previous run, an explicit pick, the project's repository, then the workspace default.
  • Create new repository makes an empty repository in your GitHub organization and links it. It needs the Starko GitHub App installed on an organization, not a personal account.
  • Auto-dispatch is off by default, so only @starko mentions start a run. A project can opt into complete bug reports, bugs and docs gaps, or small changes too.
  • Settings, Fix agent, Customer tickets picks the project that tickets filed by customers land in. If it has a repository, those tickets enter the factory: classified, then dispatched under the project's own policy.
  • Each project can have its own Slack channel where the team mentions @Starko. See Slack.
Learned context

A map of the codebase that every run starts from.

Learn project starts a research run that reads the linked repository and writes a repo map in six sections: Overview, Directory layout, Commands, Conventions, Where things live and Gotchas. Every Starko AI run gets the summary in its prompt and the full map as files it reads when it needs them. Without it, runs start from a blank page.
  • The summary is one paragraph of up to 1,500 characters. Each section is Markdown that cites file paths.
  • Edit corrects a section by hand. Saving creates a new version, and an empty section is removed.
  • Refresh researches the repository again. A map older than a month is marked so you know to refresh it.
  • Research runs are billed as agent tokens, like fix runs. Rules for the agent belong in the agent instructions, not the map.
  • Only admins and owners can learn, refresh or edit the context.

Project context

A repo map Starko AI writes by researching the repository: stack, layout, commands, conventions, where things live, gotchas. Every run gets the summary in its prompt and the full map as files it reads on demand.

EditRefresh

v3 ยท 9f2c1ab ยท learned 6 days ago

Summary the agent reads6 sections

Next.js storefront for Northwind with a Postgres database through Drizzle. Pages live in app/, checkout logic in lib/checkout. Run pnpm test lib/checkout for the fastest check of a checkout change, then pnpm typecheck.

Research runs are billed as agent tokens, like fix runs.

OverviewDirectory layoutCommandsConventionsWhere things liveGotchas
Templates

Start a project with its tickets already written.

The create dialog has a Template menu. A template fills in the icon, summary, brief, status and priority, and lists the tickets that will be created with the project, each with a priority and an optional due date counted in days from the start. Edit the list before you create, add your own, or remove what you do not need.
  • Starter templates: Project brief, Product launch, Client onboarding, Bug bash and Website redesign.
  • Save as template on any project turns its icon, summary, brief and open tickets into a reusable template.
  • Your templates stay private until you publish them. Public templates show up for everyone under their own heading.
  • The โŒ˜L assistant can create a project from a template, tickets included.
New project Project brief
๐Ÿ“Œ

Partner portal

What we are building, for whom, and why now.

Backlog Medium Sara Lind Start date
Tickets6 created with the project
  • Write the project brief2d
  • Interview target users7d
  • Define success metrics7d
  • Agree scope with stakeholders10d
  • Plan milestones12d
  • Kickoff meeting14d
  • Add a ticketโ€ฆ
Create project
Pins and sharing

Keep daily projects close, and let clients follow along.

Pin the projects you work in every day and they sit under Tickets in your sidebar, with any live Starko AI sessions listed beneath them. Share a project with the client it is for: people at the linked client, company or tenant sign in with a one-time email code and see the project's tickets and public comments in the same views your team uses.
  • Pins are per member, so they follow you and not the workspace.
  • Internal notes and the Context tab are never shared. Regenerating the link signs everyone out.
  • Who can sign in: saved contacts and shared inboxes of the linked client, company or tenant, plus anyone with an email on a linked company's domain.
  • Stop emailing the customer turns off ticket emails for internal work. Replies you mark as customer-facing still go out.

FAQAbout Projects.

Keep exploring

Connect a channel and a repository. Turn the support queue into a build queue.

Feedback starts flowing in minutes. The first recommendation shows up as soon as a pattern repeats, and the first pull request as soon as you accept one.

Start for freeGet a demo