DAYA FOR ENGINEERING

An AI agent handles the engineering work around the code

Track bugs and sprints on boards, run incidents in streams and build internal tools by describing them. When a tool needs more, a developer extends it through the API.

TRACK

Every bug linked to the customer who hit it

An issue is a row with an owner, a status and a release. See the sprint as a kanban board and the roadmap as a gantt, and link a bug to the customer conversation it came from.

What is a base? It is Daya's shared table, like a spreadsheet the whole team works in. Each row is a record, and the same rows can be viewed as a grid, a kanban board, a calendar or a gantt.
SUGGESTED SETUP
Bugs base
Linked to the ticket and the conversation that raised it.
Sprint board
A kanban view of the current sprint.
Roadmap
A gantt view of what ships when.
More about Bases →
Sprint 14
Kanban
TO DO2
Checkout fails on mobile
Bug · high
Invoice PDF export
Feature
IN PROGRESS1
Webhook retries
Feature
DONE1
Slow search on long lists
Bug
BUILD

Internal tools that never reach the backlog

Describe the tool and an agent builds it using any data in the workspace, then publishes it privately, with no repository and no deploy. Webhooks and a REST API bring in-house systems in.

SUGGESTED SETUP
Bug report app
Support files a bug and it becomes a row.
Release checklist app
The same steps before every release.
Webhooks and REST API
Events from in-house systems, in the warehouse.
More about Mini apps →
Bug report
Mini app
SUMMARY
Checkout fails on mobile
SEVERITY
High
REPORTED FROM
Rosa DelgadoInstagram
File bug
Runs on live records · no deploy step
Row added to the Bugs base
Linked to Rosa's conversation and assigned to David.
INCIDENTS AND REVIEWS

The incident review writes itself

Give each incident a stream with an owner, action items and the whole conversation in one thread. Hold the review on a call, and the transcript, decisions and action items are filed back into the stream.

SUGGESTED SETUP
Incident stream
One thread per incident, with an owner.
Action items with owners
Every follow-up has a name on it.
Review call
Recorded, transcribed and summarised by an agent.
More about Team collaboration →
# incident-checkout
Stream
14:02
Checkout errors start. David rolls back the last release.
14:06
Three customers report it in the inbox.
WhatsAppInstagramLINE
14:18
Rolled back. Checkout is working again.
Fri
Review call recorded. The summary and four action items are filed here.
The whole incident stays in one thread
RELEASES

Ship a release, and tell the people who were waiting

A release is a record that links the bugs it fixes and the features it ships. Run the same checklist before each one. When it goes out, a workflow drafts a message to the customer who reported the bug and to everyone who asked for the feature, ready for the team to send.

SUGGESTED SETUP
Releases
Each release, with the bugs it fixes and the features it ships.
Feature requests
What customers ask for, how often and from whom.
Tell them it shipped
A message to the reporter and to everyone who asked.
More about Agents & authority →
Release 2.41
Shipped on Thursday
2
bugs fixed
1
feature shipped
15
customers told
Checkout fails on mobile
Bug · reported by Rosa Delgado
InstagramFixed
Slow search on long lists
Bug · reported by the support team
Fixed
Invoice PDF export
Feature · 14 customers asked for it
Shipped
Release checklist
8 of 8 steps done · signed off by David
Complete
Fixed this release · a view of the bugs base
Instagram
Rosa Delgado was told on Instagram
“Checkout on mobile is fixed. Thank you for reporting it.” Drafted by an agent, sent by Mia.
WITH AI

Agents that read like a run log

Every agent run is saved step by step: what each step was given, what it returned, which model version it used, how long it took and what it cost. Each kind of task can use a different model.

✓Stop a run part-way and the record of what it did remains
✓Retry from the step that failed, without redoing what already worked
✓Use several model providers at once, with your own keys
How agents and authority work
ENGINEERING AGENT
CREATE
READ
UPDATE
DELETE
Bugs
●
●
●
○
Mini apps
●
●
●
○
Sprint board
○
●
●
○
Customer records
○
●
○
○
Anything outside these limits waits for a person
START HERE

Four things engineering teams set up first

BASES

Bugs base

Every report as a row, linked to where it came from.

MINI APPS

Release checklist app

Describe the steps once and reuse them.

TEAM COLLABORATION

Incident stream

One thread per incident.

VIDEO CALLS & RECORDINGS

Sprint review

A recorded call, with the notes written up.

Connects with the tools engineering teams already run

From the connector library. Webhooks and a REST API cover the rest.

GitHubGitHub GitLabGitLab JiraJira

Common questions

Do we need a developer to build a mini app?

No. Describe what is needed in a sentence. A developer can extend the app later through the API, but building one needs no code.

What if a tool we use is not in the connector library?

Use webhooks or the REST API, or have a custom connector built on Advanced.

Which models can agents use?

Models from any of the supported providers. Hold several providers at once and bring your own keys, with a workspace default and per-agent overrides on single roles.

OTHER DEPARTMENTS
Sales Marketing Customer service Operations Procurement Supply chain Finance Human resources Project management IT Security All departments

Start with engineering

Free for up to twenty people. Set up this team now, and add the others as needed.