The Basics
Learn the fundamentals of using Memex to build software through conversation.
What Makes Memex Special
Memex is designed as your complete AI development partner. Unlike other tools that require programming knowledge or limit you to templates or tech stacks, Memex handles the entire technical implementation process while you focus on what you want to build and why.
Think of Memex as having an experienced developer sitting next to you, ready to handle all the technical complexity while you describe your vision in plain language.
Understanding Memex Modes
Memex has two powerful modes designed to support different phases of your development journey.
Plan Mode vs Build Mode
Plan Mode is your strategic partner:
Acts like an experienced technical product manager
Asks thoughtful questions about your requirements
Helps scope down to a valuable MVP (Minimum Viable Product)
Considers factors you might not think of initially
Creates structured development plans optimized for Build mode
Build Mode is your hands-on development partner:
Writes and executes code directly on your machine
Installs packages and sets up development environments
Creates, edits, and manages project files
Runs applications and debugs issues
Handles complex technical implementation
When to use each mode:
Start with Plan Mode when you have a general idea but need help defining requirements and creating a development strategy
Switch to Build Mode when you're ready to implement features from your plan or work on existing projects
Return to Plan Mode when you need to think through new features or architectural decisions
You can switch between modes at any time during a conversation using the toggle at the top of the interface.
[1]
Working with Files
Giving Memex Access to Your Files
Because Memex lives and works from your computer, it can access and interact with your files. There are two ways Memex can work with your them:
Context files: These are files you'd like Memex to include in its context. This can include for example a PDF you'd like Memex to read, or an image you'd like Memex to see to help you debug something.
Content files: These are files you'd like Memex to include or reference within the tools you build. For example, if you are building a website and would like Memex to include some images you have saved in a folder.
Whenever working with files, make sure to specify to Memex what you'd like it to do with them.
There are two main ways you can point Memex to your files
Drag and drop files directly into the chat. This will add the file's path to your message.
Move files into your project directory for ongoing access. This way you can just say "use the files named file.txt saved in the project directory". You can open your project directory/folder b
[4]
For images you'd like Memex to use as Context you are also able to use the image picker, by clicking on the image icon, or by just pasting the image in. Note: using this method will limit the image usage to Context only. If you'd like Memex to use the images within the tools you build and not only as context, use one of the two methods described in the section above.
[5]
Projects
Each Memex Project corresponds to a directory on your computer and includes:
Conversations: Multiple conversations can belong to the same project
Files and Code: All your project assets in one organized location
Project Context: Custom guidelines for AI behavior (stored in
.memex/context.md
)Documentation: README files and project documentation
You can create a new project by selecting "New Project" below the conversation input. From there, you can choose to start a project from scratch, or to start one based on an existing workspace in your computer
[6]
Custom Instructions
Custom Instructions let you set consistent guidelines that Memex follows across all your conversations. Think of them as extensions to Memex's system instructions.
Useful Custom Instructions examples:
Every visualization should have a transparent background and white labels for presentations.
When transcribing audio files, default to MLX Whisper or Tiny Whisper rather than Base Whisper for better performance.
Always commit working code after each major milestone and explain what was accomplished.
When building web applications, prioritize clean, accessible design and responsive layouts.
To set Custom Instructions:
Click the wrench (🔧) icon in the interface
Navigate to Custom Instructions
Add your guidelines and preferences
[7]
Understanding Technical Outputs
Memex organizes technical operations (code execution, web searches, file operations) in collapsible sections to keep conversations clean and focused.
[Insert technical outputs walkthrough here]
What you'll see:
Code execution results and outputs
Web search queries and results
File operations like creation and editing
System commands and their responses
You can expand any of these sections to see the details or copy content for your own use.
Next Steps
Now that you understand the basics:
Try Plan Mode with an idea you'd like to explore
Create a simple project in Build Mode to get hands-on experience
Experiment with file uploads and data analysis
Set up Custom Instructions that match your preferences
Read our Best Practices Guide for advanced techniques
Remember: the best way to learn Memex is by using it. Start with something simple that interests you, and don't be afraid to experiment and ask questions along the way.
Last updated
Was this helpful?