A familiar editor
Monaco-powered editing, syntax highlighting, file tabs and a file tree that stays where you expect it. Work locally or in your selected SSH workspace.
Creaneo Code · IDE / CLI / Web
Your code.
Your tools.
Your momentum.
Build with an AI partner in a familiar workspace. Edit your project, connect a server, check your app in the browser, and keep your next step in view.
100 free requests, once per account. Shared across Creaneo IDE, CLI and web chat. No card required.
Real IDE capture with a demonstration project. Desktop build availability is listed on the download page.
Inside the workspace
Everything stays in context.
A consistent layout, from your first file to your final preview. Explore what is implemented today, with clear boundaries on what each feature can do.
A real terminal
Run your development tools in an integrated PTY terminal. Shell execution is real access to your machine—not a simulated console or an OS sandbox.
AI with project context
Ask, explain, debug and make changes with selected project context. Review proposed edits and keep the conversation beside your code.
Review, Auto and Ask
Use Shift+Tab to switch agent modes. Review changes first, allow eligible edits in Auto, or discuss in Ask. Command permissions remain separate.
Remote SSH
Connect to your own server, browse files over SFTP and work in a remote terminal. Host-key confirmation and changed-host checks help protect connections.
Browser inside the IDE
Open your running HTTP or HTTPS app, inspect page text and console output, and preview a remote service through SSH forwarding.
Task checkpoints
Review, restore and redo local Creaneo AI file changes with conflict checks. Checkpoints do not undo arbitrary terminal commands, third-party CLI edits or SSH changes.
Protected file writes
Expected-content checks catch changes made since an edit was proposed. Local writes use atomic replacement with path and symlink checks.
Git alongside your code
Inspect project Git status and changes, with the integrated terminal available for your Git workflow. Keep normal version control as your source of history.
Find your way around
Navigate project files and search through your workspace. Choose the context you want to bring into the conversation.
Bring your own CLI
Connect locally installed Codex CLI or Claude Code in the AI area. They use your own provider account, settings and permissions. This is not a VS Code extension host.
Space, in the same layout
Preview shared AI conversations, participant and provider labels, opt-in code attribution and team todos. Your files stay left, work stays central and AI stays right.
From request to review
Build. Check. Keep control.
01
Open your project
Choose local files or connect your own SSH server. Keep credentials in your own environment.
02
Choose your AI
Use Creaneo or connect your local Codex / Claude CLI. Choose the agent mode for the task.
03
Review the work
Inspect suggested changes and command requests. Local Creaneo edits can be grouped into task checkpoints.
04
See the result
Run your app and open the IDE browser. Test the actual result before you commit or deploy.
Auto mode is a permission setting—not a security sandbox. Review untrusted projects and commands. Keep backups and Git history; an AI cannot guarantee a correct or safe change.
IDE 0.1.6 · Available in the signed desktop update
Different agents.
The same place to build.
Creaneo AI, Codex and Claude belong beside your code—not in a different workspace. Native chat, simpler Space invitations and recent SSH connections now share the same IDE layout.
cndashboard.tsx✦ Space
FILES
dashboard
dashboard.tsx
package.json
dashboard.tsx
export function Dashboard() {
return (
<main>
<h1>Your team, together.</h1>
<ProjectList />
</main>
);
} Editor and terminal stay in place.
● CodexLOCAL PROJECT
Review the dashboard’s empty state.
Codex
I’ll inspect the component and show the proposed changes here.
Read dashboard.tsx
Ask about your code…
+ File / selection
Interactive design illustration, not a live AI session. Native external chats use your installed CLI, provider account and permission rules. They do not spend Creaneo credits.
Name it. Copy it. Invite.
Enter only your Space name. The current project label is detected automatically. Your invitation stays at the bottom of the Space panel with a one-click Copy control.
Space code · Example only
DEMO-SPACE-CODECopySingle-use codes expire after 15 minutes and renew while Space is open. The owner still approves new members.
A steadier conversation.
Streaming replies update the message, not the whole IDE. Keep your draft, cursor and expanded tool cards in place. Send and Stop use the same compact visual style as Creaneo.
Your servers, one click away.
Successful SSH connections appear in Recent connections. Reconnect in one click during the session, or opt into secure password storage on a supported system keyring to reconnect after restarting. Without secure storage, enter the password again. History stays on your device.
Password-only PAM / keyboard-interactive login is supported. Server permissions still apply; OTP and additional verification may require a terminal.
Planned · Not available yet
On the same server?
A proposed, opt-in teammate prompt: see who is working on the same SSH server and choose whether to open Space together. A name and profile photo, shown once per app launch.
Discovery permissions and privacy controls are still being designed. No server-presence discovery is active in the current release.
Chat, invitation and SSH improvements are included in the signed 0.1.6 update. Linux package and upgrade flow tested; native Windows and macOS packages have not been validated here. The same-server teammate prompt remains a roadmap concept.
INTRODUCING SPACE Team hub · IDE 0.1.5
Your team. Your AI conversations. Together.
Great minds.
Shared context.
Same files. Same editor. Your team’s AI conversations, right beside your own. Space brings collaboration into the IDE you already use.
Take the visual tourSign in · create a Space · invite your team
SpaceTEAM CONTEXT
N
NoraCreaneo AI · Interface
E
EmreCodex · API discussion
L
Illustrative team · independent AI sessionsLinaClaude · Test planning
CREATENANO IDE / SPACEDemo workspace
Know the contributor.
Names, profile avatars, personal colors and reported AI labels beside matching-version code.
One team. Different AIs.
Creaneo AI, Codex and Claude session labels. Shared conversations stay in the right panel.
Claim a todo. Keep control.
A shared board in the center. Bring a task to your own AI with existing approval rules intact.
AVAILABLE NOW · LOCAL PROJECT SHARINGYour code.
Your code.
On their screen.
Open the small Space button at the bottom of the IDE. Create a Space and copy the invitation shown at the top. Approve your teammate, review the saved source files you want to publish, and they can open them from their left Explorer in the same editor layout.
Files are read-only snapshots, not a live shared drive. Review and republish to send changes. Up to 100 source files, 64 KiB per file and 512 KiB total. Selected source is stored on Createnano and visible to approved members; check for embedded secrets before sharing.
AVAILABLE IN 0.1.5 · TEAM HUB
From a project team to your company.
Create a company, connect with friends through approved invitations and choose whether to appear online. Keep projects in your company directory, request access or send a direct in-app invitation to a teammate. Company membership does not automatically unlock private project files.
Open Space → Team hub. Company and friend codes are single-use and expire after 15 minutes. Direct project invitations arrive inside the IDE, not by email. Company names are self-declared, not verified business identities. TEAM HUB / COMPANY & PROJECTSIDE 0.1.5
TEAMMATE VIEW / SHARED SOURCERead-only snapshot
FROM “WHAT ARE YOU WORKING ON?” TO “I SEE IT.”
Less catching up.
More working together.
Scroll through the workflowInvite & approve / Actual beta interface
Invite your people.
Send a short-lived, single-use code. The owner approves each new member before shared conversations become visible.
Another AI. One tab away.
See each session owner and their declared AI: Creaneo AI, Codex or Claude. Scroll between shared conversations and return to My AI without leaving your code. CLI transcripts are not shared automatically.
Add your perspective.
Read the proposal, ask a question and leave a comment. Shared messages carry the identity of the person who published them.
Share on your terms.
Choose when new AI messages become team-visible. Existing chats stay private; stop future sharing whenever you need to.
A name beside the code.
See a teammate’s color, name, avatar and reported AI beside contributed lines. Upload a profile photo or use initials. Labels appear only when your file matches the shared version; they are client-reported contributions, not verified git authorship.
Claim it. Bring your AI.
Open Todo beside Browser. Claim a task, see who is doing what and send your task to your own Creaneo AI. Connected Codex and Claude CLIs receive a draft for you to submit. The AI does not mark tasks done automatically.
LOOK CLOSER
Seven views. One Space.
Working in SpaceShared work.
Shared work.
Clear boundaries.
Invitations, comments, provider labels, profile photos, opt-in contribution metadata, team todos and owner-published local source snapshots are implemented. File attribution requires matching content and an explicitly linked project. Selected source files are uploaded only after review and consent. Space refreshes about every three seconds; it is not keystroke-level co-editing.
IN DEVELOPMENT — NOT AVAILABLE YET
The next chapter is shared execution.
Shared SSH files, actually taking over another AI, shared task diffs and team-wide undo are still being built. Coordination handover in today’s interface does not run another person’s AI.
Get the IDE Sign in to create a Space. Joining an existing Space requires its owner’s approval.Creaneo CLI
Stay in your terminal.
Move the project forward.
A standalone coding agent for your current directory. Ask it to inspect code, propose file changes and run commands—with explicit approval by default.
- ↳ Browser-based sign-in; no API key to paste
- ↳ File reads, proposed edits and approved shell commands
- ↳ Chat-only mode when you do not need file access
- ↳ Token usage, request quota and actionable connection errors
- ↳ One account balance with Creaneo IDE and web chat
Terminal · Quick start
# Install from the download page, then:
creaneo-code login
# Enter your project directory
cd your-project
creaneo-code
# Or use chat without file tools
creaneo-code chat
# Check your account
creaneo-code meReview installer scripts before running them. Agent follow-up calls each use one Creaneo request.
Registration is open
100free requests
One account. Three ways to build.
01 / Sign up and verify. Complete the human check and start immediately. No administrator approval or payment card for a new account.
02 / Use your free allowance. 100 successful AI requests, once per account, shared across IDE, CLI and web chat—not 100 per tool or per day.
03 / Subscribe when you need more. Continue with your paid plan allowance. Buying and using extra credit packs requires an active subscription.
Before you begin.
How do the 100 free requests work?
Create an account and complete human verification. You receive 100 successful Creaneo AI requests once per account, shared across IDE, web chat and Creaneo CLI. They do not reset daily. No payment card is needed.
Does one agent task use one request?
Not always. Each successful call to Creaneo AI uses one request, including an agent's follow-up calls after tools. A multi-step task can use several requests. Failed AI responses are refunded.
What happens after the free requests?
Subscribe to continue with your plan allowance. Extra credit packs require an active subscription to buy and use. Purchased balances stay saved if your subscription ends; they become usable again with an active subscription.
Does connecting Codex or Claude use Creaneo credits?
No. Those local CLIs use their own provider accounts and billing. Creaneo does not include a Codex or Claude subscription, copy their credentials into your account, or remove their permission checks.
Is Space available to everyone?
Sign in with IDE 0.1.5 or later for Space and Team hub: companies, mutually accepted friends, optional online status and a project directory. Company membership and project access are separate permissions. Invitations use short-lived codes or an in-app project inbox. Reviewed local source is shared as read-only snapshots; live co-editing and control of another member's agent are not available yet.
Will my history sync between all tools?
Your login identity, subscription and Creaneo request balance are shared. Web conversations are saved to your account. Local CLI and IDE conversation histories are not automatically merged into web history.
Can I install VS Code Marketplace extensions?
Not currently. Direct CLI connections are supported, but this build does not provide a VS Code Marketplace extension host or automatic IDE updates.
Which desktop builds can I use?
The download page lists the builds actually available. The current Linux desktop package is a test build. Cross-platform signing, automatic updates and broader release validation are still in progress. Web registration and Creaneo CLI access are open.