An agentic product workspace for your whole team
Ask from Slack or open a thread in Gently. No local installs for teammates.
Engineering asks
Couriers need to set when they can work, so operations can offer each route to someone available that day.
Task prompt
Let couriers set their availability, and only offer routes to couriers available that day.
Gently handles the environment
Gently gets your project running with minimal supervision: installing packages, resolving version conflicts, starting services, and checking the app. PMs, designers, and the rest of the team can get to work without following an install guide.
Each thread has its own isolated development environment. If an experiment breaks one, other threads keep working. The whole team does not have to wait for someone to repair a shared environment.
Let Gently set up your projectOne connected project
Crosstown’s repositories and saved setup
Thread 1 · Product
Explore delivery options
Own code, dependencies, services, and preview
Thread 2 · Design
Sketch courier availability
Own code, dependencies, services, and preview
Thread 3 · Engineering
Build recipient tracking
Own code, dependencies, services, and preview
Work together inside a thread. Explore independently across threads. Gently can diagnose and fix setup problems in the conversation.
Start with something that matters
A feature customers keep asking for. A bug that blocks their work. A question your team needs answered. Bring it into Gently and take it through to a result.
Take a customer request through implementation, testing, and release. Build across the interface, APIs, and database, with a working preview and changes your team can review and deploy.
“Let couriers set their availability, and only offer routes to couriers available that day.”See how teams ship
Resolve bugs in the flows your customers depend on. Reproduce the problem, make the change, and check the full flow before your team releases it.
“Two couriers try to accept the same route. Check that only one succeeds and the other gets a clear response.”See how review works
Ask from Slack when a customer needs an explanation. Gently checks how your product works and replies in the thread, so you can ask follow-up questions and share the answer with your team.
“A courier accepted a route but cannot finish a delivery. What should they do, and what will the customer be told?”Get your first answer
Gently in Slack
Support needs an explanation. Sales needs to check a promise. Product needs to understand a flow. Ask Gently where your team already works, with answers grounded in your connected code and tools.
Example Slack exchanges · Crosstown, a fictional delivery app
@gentlybot In Crosstown, what happens when a courier cannot finish a delivery?
The courier marks the stop “Could not deliver” and chooses a reason. If the customer has an email address, Crosstown tells them the delivery failed and the order is returning to the shop. The shop arranges another delivery.
In a channel, mention Gentlybot again in your thread reply to ask a follow-up. The conversation continues in the same Gently thread.
Connect Slack →One product, different questions
These are real Gently threads using Crosstown, a fictional delivery app. The same connected code helps each team understand what the product does.
Customer support asks
A courier cannot complete a delivery. Support needs to explain the next step and what the customer will hear.
Task prompt
A courier accepted a route but cannot finish a delivery. What should they do, and what will the customer be told?
Sales asks
A shop wants to know whether its customers can track deliveries and see proof of delivery.
Task prompt
Can customers track their delivery and see a proof photo in Crosstown today?
Can customers track their delivery and see a proof photo in Crosstown today? Follow-up: Give me the short version I can use before a sales demo.
Work in the same thread
Share the thread with the people who know the problem. They can add context, open the working app, test a change someone else built, and leave feedback beside the work.
Review a teammate’s workAdd shared owners to work on the feature together. Teammates can contribute context, mention each other, and follow updates as the work moves forward.
Open the thread’s preview and try the full flow, even when someone else started the run. Check edge cases and add what you find to the conversation.
Keep feedback, screenshots, checks, and code changes beside the request. Continue the work in the same thread and take the feature through release together.
The evidence is part of the work
Open a teammate’s preview, check the full flow, and review the code and browser evidence together. Keep the findings in the shared thread as your team takes the feature through release.
How to test and review togetherQA asks
A courier accepts a route, delivers one order, and cannot deliver another. QA needs to check what happens next.
Task prompt
Test that a courier can accept a route, deliver an order, and mark another delivery as failed. Check the customer emails too.
Test that a courier can accept a route, deliver an order, and mark another delivery as failed. Check the customer emails too. Follow-up: Re-test accepting a route, delivering one order, and marking another delivery failed in the browser. Use demo orders with customer email addresses and check both emails. Follow-up: Summarize the completed browser checks and the two verified emails in a short checklist.
Proof you can play
Real Crosstown walkthroughs recorded and narrated by Gently, with subtitles. Press play to follow the flow and see its result.
Follow the courier’s availability flow and see the saved result.
Gently recording · Narration and English subtitles · Fictional demo data
Walk through the customer’s delivery tracking page.
Gently recording · Narration and English subtitles · Fictional demo data
Gently on the go
Ask a product question, read the answer, and keep the conversation moving from your phone. The same project and thread are there when you get back to your desk.
Here, a quick question checks whether Crosstown customers can track their delivery.
Start your first threadEarly teams, real work
Production usage across our first teams, May–August 2026.86%
of pull requests opened from threads get merged
1.2 h
median from first prompt to merged PR
745
threads where Gently checked its own work in a real browser
1 in 3
threads are questions and research, not code changes
36
people prompting, from engineering to sales
Observed usage from our first teams; results vary by project and task. See the workflow behind the numbers.
Yes. Once your workspace connects Slack, mention Gentlybot in a channel or send it a direct message. It checks your connected code and tools and replies in Slack. Attach screenshots, answer its clarifying questions, and mention it again for follow-ups in the same channel thread. Open the linked Gently thread when you want to inspect previews or continue deeper work.
Product, design, support, engineering, and the teammates who need to understand or improve a software product. Start with a question, explore a request, or ask for a change directly. Engineering can use the same workspace for investigations, fixes, and review.
Yes. Shared owners can work on and manage a thread together. Teammates can add context and comments, open previews to test each other’s changes, and follow updates. The request, evidence, and feedback stay together through review and release.
Yes. Connect the repositories that make up your product and ask Gently to get it running. Gently inspects the project, configures dependencies and services, and checks the app with minimal supervision. Teammates can then start threads without repeating the setup on their own machines.
Each thread has its own isolated environment. A broken install or experiment in one thread does not change the environments in other threads. Ask Gently to diagnose and fix the problem in that thread while the rest of the team keeps working. Teammates in the same thread share its environment and preview.
No. Once the project is set up, teammates work through Gently and open the thread’s running preview. Gently handles the dependencies, tool versions, and services in the environment. Project owners provide any access or configuration details Gently cannot infer.
Gently works in an isolated environment and produces reviewable changes. Your team can inspect the preview, the available verification evidence, and the pull request before using its normal review and merge process.
You pay per builder. Teammates who ask questions, review plans, and open previews can participate without a builder seat. See the pricing page for plan details, usage, and available controls.
Connect your app and bring a feature request into a shared thread. Invite the people who know the problem, and take the work through to release.
Request access and we’ll email you when we can onboard your team. Pay per builder, not per teammate.