​
Join the waitlist

To get early access to Asimov, sign up via our waitlist. We’ll email you once your access is ready.

​
Setting up Asimov

Once you’ve been granted access, getting started takes just a few steps. Asimov will walk you through the initial setup:

  • Login with your email: We’ll send you a one-time verification code—no passwords needed.
  • Accept or create your workspace: You can either accept an invitation from an existing team or create a new workspace.
  • Invite your teammates: Asimov gets more useful when it understands your team’s knowledge and decisions. Invite collaborators to join and assign appropriate roles (Owner, Admin, Member).
  • Set up integrations: Asimov needs access to your codebase to start working. You can include private and public GitHub repositories, along with other relevant sources of technical context, such as team communications.

Once integrations are added, you’re ready to start asking questions and exploring your systems with Asimov!

​
Ask your first question

​
Selecting context sources

Asimov tailors its answers based on the context you give it. That means it won’t return anything until you’ve selected at least one connected source—like a GitHub repository—to reference. You can think of this step as setting the “scope” for your question.

Just click the + icon and choose which sources you want Asimov to draw from. You can select individual sources, or use Add All to enable Asimov to reason over your entire workspace. The more sources you include, the more context Asimov has to work with—though this may slightly increase the time it takes to return a response.

​
Try asking one of these questions

Asimov can help across many areas of your development process. Here are some example questions, organized into four categories to help you get started.

​
Onboarding

Get up to speed with your codebase structure and setup:

  • “What is the overall architecture of this repository?”
  • “Can you provide a high-level overview of the main services or modules?”
  • “How do I set up and run this project locally?”

​
Engineering

Dive deep into technical implementation details:

  • “What are the security considerations and potential vulnerabilities of our authentication setup?”
  • “How does error handling work across different modules?”
  • “What are the database schema relationships and constraints?”

​
Velocity

Identify opportunities to improve development speed and code quality:

  • “What are the most complex functions that could be simplified in our agent?”
  • “Where can we reduce code duplication or improve reusability?”
  • “What are the performance bottlenecks in the current implementation?”

​
Tribal knowledge

Uncover team discussions and institutional knowledge:

  • “What were the key architectural decisions discussed by the team?”
  • “What are the recent blockers or issues mentioned by the team?”
  • “What are the main pain points mentioned in Slack about our codebase?”

​
Next steps