Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/21st-dev/1code/llms.txt

Use this file to discover all available pages before exploring further.

​
Getting Help

We’re here to help you get the most out of 1Code. Choose the support option that best fits your needs:

​
Community Support

Discord Community

Best for: Quick questions, real-time help, feature discussionsJoin our active Discord community to:
  • Get help from other users and the core team
  • Share tips and workflows
  • Stay updated on new features
  • Report bugs and discuss feature requests
Response time: Usually within a few hours during business hours

GitHub Issues

Best for: Bug reports, feature requests, technical issuesUse GitHub Issues to:
  • Report bugs with detailed reproduction steps
  • Request new features
  • Track issue resolution
  • Search existing issues
Response time: 1-3 business days

GitHub Discussions

Best for: Questions, ideas, general discussionUse Discussions for:
  • Asking how to do something
  • Sharing workflows and use cases
  • Discussing feature ideas before creating an issue
  • Community Q&A
Response time: 1-3 business days

Documentation

Best for: Learning how to use 1CodeOur documentation includes:
  • Getting started guides
  • Feature explanations
  • API reference
  • Troubleshooting tips
Always available

​
Premium Support

Subscribers to 1code.dev get additional support benefits:

Private Discord Channel

Available for: Pro and Max subscribers
  • Direct access to the core team
  • Priority response times
  • Private channel for sensitive discussions
  • Early access to new features

Email Support

Available for: Max subscribers
  • Direct email support: support@21st.dev
  • Faster response times (usually within 24 hours)
  • Help with complex setups and integrations
  • Priority bug fixes
Premium support is included with 1code.dev subscriptions. Open-source users have access to community support.

​
Before Asking for Help

To get the fastest resolution, please:
1

Check the documentation

Search our documentation for your question. Common topics:
2

Search existing issues

Someone may have already reported your issue:
3

Gather information

Before asking for help, collect:
  • OS and version (macOS 13.4, Windows 11, Ubuntu 22.04, etc.)
  • 1Code version (check in Settings → About)
  • Build type (open source build or 1code.dev subscription)
  • Error messages (full text or screenshots)
  • Steps to reproduce (what you did before the issue)
  • Expected vs actual behavior

​
Reporting Bugs

When reporting bugs, include:

​
Required Information

  1. Clear description of the problem
  2. Steps to reproduce the issue: 
    1. Open 1Code
2. Create a new chat
3. Click X button
4. Error appears
  3. Expected behavior: What should happen
  4. Actual behavior: What actually happens
  5. Environment:
    • OS and version
    • 1Code version
    • Build type (open source or 1code.dev)

​
Optional but Helpful

  • Screenshots or videos showing the issue
  • Logs (if applicable):
    • macOS: ~/Library/Logs/1Code/
    • Linux: ~/.config/1Code/logs/
    • Windows: %APPDATA%/1Code/logs/
  • Console errors (open DevTools with Cmd+Option+I or Ctrl+Shift+I)
  • Workarounds you’ve tried

​
Where to Report

Critical Bugs

Data loss, crashes, security issues - create a GitHub issue immediately

Minor Bugs

UI glitches, small errors - report in Discord first

​
Requesting Features

We love hearing your ideas! Here’s how to request features:
1

Check if it already exists

Search:
2

Start a discussion

Before creating an issue, start a discussion to:
  • Gauge community interest
  • Get feedback on the idea
  • Refine the proposal
3

Create a feature request

If there’s strong interest, create an issue with:
  • Problem statement: What problem does this solve?
  • Proposed solution: How should it work?
  • Alternatives considered: Other approaches you thought of
  • Use cases: When would you use this?
  • Mockups (if applicable): Screenshots or sketches
Features that solve common problems and align with 1Code’s vision are more likely to be implemented.

​
Contributing Code

The fastest way to get a feature is to build it yourself!
  1. Read the Contributing Guide
  2. Set up your development environment
  3. Join Discord to discuss your approach
  4. Submit a Pull Request
We’re happy to help new contributors. Don’t be afraid to ask questions!

​
Support Response Times

Expected response times by channel:
ChannelOpen SourceSubscribers
DiscordFew hours - 2 days1-4 hours*
GitHub Issues1-3 business days1 business day
GitHub Discussions1-3 business days1 business day
EmailNot available24 hours (Max plan)
*During business hours (Mon-Fri, 9am-5pm PT)

​
Emergency Support

For critical production issues (Max subscribers only):
  • Email: support@21st.dev with “URGENT” in subject
  • Response time: 2-4 hours during business hours
What counts as critical:
  • Data loss
  • Security vulnerabilities
  • Complete service outage
  • Breaking bugs in production
What doesn’t:
  • Feature requests
  • Questions
  • Minor bugs
  • Enhancement ideas

​
Self-Service Resources

Troubleshooting

Common issues and solutions

FAQ

Frequently asked questions

Changelog

What’s new in each release

API Docs

Programmatic access to 1Code

​
Community Guidelines

When seeking help:
  • Be respectful to everyone
  • Be clear about your issue
  • Be patient - maintainers are volunteers or have limited time
  • Be helpful - share solutions you find to help others
  • Search first - avoid duplicate questions

​
Feedback

We’re always looking to improve. Share your feedback:
  • What’s working well? Tell us in Discord
  • What’s confusing? Help us improve the docs
  • What’s missing? Request features on GitHub
  • What’s broken? Report bugs
Your feedback shapes the future of 1Code!

​
Contact

Discord

Join the community

GitHub

View source code

Website

Visit 1code.dev

Twitter/X

Follow for updates

Documentation

Read the docs

Blog

Latest articles

Build docs developers (and LLMs) love

Get started for freeTalk to us