Starko, inside your Slack.A foreman per project, an assistant in DMs.
Connect Slack once and Starko works in two places. In a project's channel it files tickets, starts Starko AI fixes and reports on them for the whole team. In a direct message it is your own assistant. Anything that changes data waits for an Approve or Decline card.
@Starko three customers on big accounts say the CSV export times out after a minute. File it as a bug and start a run.
export-timeout.pngFiled CSV export times out for large accounts on Northwind Web as a bug, with your screenshot attached. A run needs an approval first:
Start a Starko AI run on this ticket. It opens a draft pull request in the repository; the run and the PR show on the ticket page.
Ticket: CSV export times out for large accounts
Repository: northwind/web
Profile: Bug · small
Approved by Luka Petrović
🚀 Starko AI on CSV export times out for large accounts
Bug · small · pull request ready · 14 min
Reproduction reproduced · 3 checks run · Fix #412 · CI success · Review low risk
Exports over 10,000 rows now stream to the browser instead of being built in memory, so large accounts no longer hit the 60 second limit.
Reviewer: small, contained change with a test for a 40,000 row export.
Looks good, thanks. Luka will review it.
Slack in short.
- Connect
- Workspace owners connect Slack under Settings, Integrations.
- Project channel
- One channel per project, picked by an owner or admin in the project's Starko AI settings.
- Who it answers
- Members of your Starko workspace, matched by their Slack email.
- Acts as
- The person asking. An approval runs with the permissions of whoever clicks Approve.
- Approvals
- Cards expire after 24 hours, and a second click never runs an action twice.
- Files
- Up to 10 files per ticket, 25 MB each, carried over from the thread.
- Memory
- Reads the newest 40 messages of the thread it is answering in.
- Same agent
- The tools of the ⌘L assistant, minus the on-screen ones.
Connect Slack, then give each project its channel.
- Starko joins public channels by itself. For a private channel, invite @Starko first.
- A channel belongs to one project. Channels already taken show which project they are bound to.
- Disconnecting the channel in the same card makes Starko leave it.
- Slack is also a support channel: messages in channels that are not bound to a project, and DMs from people who are not on your team, land in the Inbox as Slack conversations. See Slack for customer support.
The project's notes for the agent: stack, conventions, areas to avoid. Trusted context in every run.
Pick the channel where this project's team works. Mention @Starko there to work on tickets, dispatch fix runs and check load. Every change gets an Approve / Decline card.
The foreman: mention @Starko and the work stays in the thread.
- New tickets are announced in the channel, once per ticket.
- When a Starko AI run needs information, its question is posted in the channel. A reply in that thread answers it and resumes the run.
- When a pull request is ready, the channel gets it with the reviewer's verdict.
- "Merge it" in the thread merges a Starko AI pull request for owners and admins. See review and merge.
- Someone whose Slack email is not on your Starko team gets a private note instead of an answer.
Every change with consequences is a card with two buttons.
- Any member of the workspace can click, and the action runs with the clicker's permissions, not the asker's.
- Cards expire after 24 hours. A double click cannot run an action twice.
- Forward status moves, priority, dates and assigning a ticket to yourself happen at once, without a card.
- Approving a recurring ask saves the workflow and switches it on.
In a DM, Starko is your personal assistant.
- Starter prompts: What's waiting on me?, Overdue tickets, Team load and SLA risk.
- Ticket rows have Open, Assign to me and Fix with Starko AI. Fixing needs an owner or admin.
- Recommendations from Improvements have Accept and Decline. Decline asks why, with the same reasons as the app.
- A card shows up to 8 rows. Ask to narrow it down for the rest.
Which tickets are overdue, and who owns them?
Three are overdue. Two are yours and the VAT one is Luka's.
CSV export times out for large accounts
Open · Urgent · due 30 Oct
Coupon field accepts expired codes at checkout
Open · High · due 31 Oct
Invoice PDF shows the wrong VAT number
In progress · High · due 1 Nov
One live card per run, edited in place.
- Phases: preparing, booting the sandbox, working, waiting for an instruction, wrapping up.
- Endings: needs an answer, pull request ready, merged, finished, stopped or failed.
- While it works, the card shows the agent's last three steps. When it ends, it shows the summary and the reviewer's assessment.
- Buttons open the ticket and the pull request. See cloud sandboxes for where the run happens.
❓ Starko AI on Coupon field accepts expired codes at checkout
Bug · small · needs an answer · 9 min
Reproduction reproduced · 1 check run · Fix waiting for an answer
Reply on the ticket (or in this thread) to resume the run.
Show an error under the field: "This code has expired." Don't block the order.
Recurring asks, and screenshots that end up on the ticket.
- Schedules run every hour, or daily or weekly at a whole hour, in UTC.
- A scheduled step can start a Starko AI coding session.
- Up to 10 files per ticket, 25 MB each.
FAQAbout Slack.
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.