Her finner du en samlet, strukturert oversikt over hvordan GoRabbit fungerer – for kunder, tekniske brukere og governance/styring.
The proprietary internal mechanism handled automatically by the system.
RabbitAgent is the publishing module of GoRabbit. While RabbitEngine plans, analyzes, and organizes the publishing work, RabbitAgent physically performs the publishing inside a browser using Playwright. The proprietary internal mechanism handled automatically by the system. In other words, the proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system.
RabbitEngine is the brain — it builds queues, analyzes segments, applies proprietary internal mechanism handled automatically by the system. RabbitAgent is the hands — it opens the browser, navigates, clicks, pastes text and images, publishes, and reports status back. This separation makes the system extremely stable, scalable, and easy to maintain.
Publishes via a real Playwright browser.
RabbitAgent uses Playwright as the proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. This makes the publishing look completely natural to Facebook, dramatically reducing the risk of restrictions.
proprietary internal mechanism handled automatically by the system.
If a publishing attempt fails — due to timeout, HTML changes, group restrictions, or Facebook loading issues — the proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. This prevents the proprietary internal mechanism handled automatically by the system.
Mimics humans to avoid restrictions.
The proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. This is the foundation for posting in hundreds of groups without being blocked.
proprietary internal mechanism handled automatically by the system.
Publishing involves many steps: (1) Open browser. (2) Load Facebook using cookies. (3) Navigate to the group. (4) Wait for the ‘Create Post’ box. (5) Read proprietary internal mechanism handled automatically by the system. (6) Enter text. (7) Upload image. (8) Click ‘Post’. (9) Verify the post was published. (10) Report status back to proprietary internal mechanism handled automatically by the system. Everything happens sequentially and is logged to Slack.
Uses separate, isolated Playwright profiles.
Yes. The proprietary internal mechanism handled automatically by the system. It operates in dedicated Playwright profiles that contain cookies and settings isolated from all other data. This makes the system more secure and prevents personal browsing data from conflicting with automation. It also avoids unexpected UI changes triggered by Facebook’s Personal Feed.
Uploads images via Playwright.
The proprietary internal mechanism handled automatically by the system. The image must reside in the campaign directory defined by the proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.
Speed is controlled by the proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. All macro timing (posting time, intervals, proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. This ensures stable and natural behavior.
Mimics natural behavior to avoid flags.
RabbitAgent avoids spam behavior by never posting in rapid sequence, using randomized click positions, waiting for DOM stability, scrolling naturally, and inserting realistic pauses. Combined with proprietary internal mechanism handled automatically by the system.
Reports status and details to the proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system.
Yes — logs details to Slack.
Yes. The proprietary internal mechanism handled automatically by the system. Slack serves as the operations cockpit for both proprietary internal mechanism handled automatically by the system.
One proprietary internal mechanism handled automatically by the system. More Agents = parallel run.
In the current architecture, each RabbitAgent runs one browser instance at a time. For parallel publishing, multiple proprietary internal mechanism handled automatically by the system. This keeps the system flexible and scalable without introducing complex threading issues.
Reads proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. It only needs what the proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
Status files and Slack updates.
The proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
Start via Python, stop via SIGTERM or empty proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. The typical workflow is launching it from the terminal using: `python3 rabbit_agent.py`. The proprietary internal mechanism handled automatically by the system. It also has a safe-stop mechanism to avoid half-published posts.
proprietary internal mechanism handled automatically by the system.
RabbitAgent is stateless. It reads everything it needs from proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. This volatile state is deleted when the proprietary internal mechanism handled automatically by the system. All permanent state belongs to the proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system.
RabbitAgent is highly stable in daily operation because it relies on Playwright, which is robust to DOM changes and network fluctuations. The proprietary internal mechanism handled automatically by the system. It typically runs for hours or even multi-day campaigns without issues.
Detects changes and stops safely.
When Facebook updates its UI or changes DOM structure, the proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. Minor HTML changes are handled through fallback selectors. Major changes may require small updates to the proprietary internal mechanism handled automatically by the system.
Yes — full proxy support.
Yes. The proprietary internal mechanism handled automatically by the system. This is useful for multi-country publishing or when Facebook requires region-specific IPs. Proxy settings are stored in proprietary internal mechanism handled automatically by the system.json.
Yes — mobile DOM fully supported.
Yes. Facebook sometimes displays mobile UI on desktop for certain groups. The proprietary internal mechanism handled automatically by the system. Mobile UI support is built-in to prevent failed publishing events.
Checks access automatically via DOM and redirects.
The proprietary internal mechanism handled automatically by the system. If the account does not have access, Facebook shows alternative pages such as 'Content not available'. The proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. All ordering logic resides in proprietary internal mechanism handled automatically by the system.
Uses ~400–900 MB RAM, normal for browsers.
The proprietary internal mechanism handled automatically by the system. Typical values range from 400–900 MB per instance, depending on the number of tabs and Facebook’s resource usage. This is normal for a browser automation module.
CPU between 5–25%, higher on image uploads.
The proprietary internal mechanism handled automatically by the system. Typical usage is between 5–25%, but can peak higher when uploading images or navigating heavy DOM structures. This is normal and expected.
Headless for testing only, not production.
Yes, but only in test and staging environments. Headless mode is not used in production because Facebook can sometimes detect headless browsers. In production, the proprietary internal mechanism handled automatically by the system.
Yes — multiple accounts via separate cookies.
Yes. Each account receives its own session folder and cookie proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. This makes it possible to run campaigns for multiple clients on one machine, but each account must have its own authenticated cookie.
Yes — safe with normal activity.
Yes, as long as proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. However, it’s important to use an account that does not violate Facebook’s terms and avoid commercial spam. The system protects the account by keeping posting within natural boundaries.
Error logged, job halted, retried later.
If the browser crashes, the proprietary internal mechanism handled automatically by the system. The job is flagged as 'failed' in the proprietary internal mechanism handled automatically by the system. No half-posted content remains. The operator can restart the proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. If Facebook is slow, the proprietary internal mechanism handled automatically by the system. This prevents incorrect clicks or premature publishing.
Attempts fallbacks, stops on failure.
The proprietary internal mechanism handled automatically by the system. If none work, a Slack error is sent and the job is halted to avoid risk. This can happen if Facebook updated its UI, if the group is down, or if the account is temporarily restricted.
Yes — full multi-machine support.
Yes. The system is designed for distribution. Multiple proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system. This makes GoRabbit scalable with almost no upper limit.
No — proprietary internal mechanism handled automatically by the system.
No. The proprietary internal mechanism handled automatically by the system. Facebook may compress them after upload, but the proprietary internal mechanism handled automatically by the system. This ensures 1:1 content quality from campaign files to final posts.
Yes — natural mouse simulation.
Yes. The proprietary internal mechanism handled automatically by the system. The cursor never jumps directly from point A to B but follows natural curves through intermediate points. This is critical for mimicking genuine user behavior.
DOM is checked before every interaction.
Yes. The proprietary internal mechanism handled automatically by the system. If the DOM is unstable, the proprietary internal mechanism handled automatically by the system. This prevents mis-posts.
Yes — takes screenshots on failure.
Yes. On critical errors, the proprietary internal mechanism handled automatically by the system. This makes it possible to analyze what went wrong — such as UI changes, warnings, or missing elements.
Yes — but prefers fast paste for stability.
Yes. The proprietary internal mechanism handled automatically by the system. However, it does support natural-typing mode if needed.
Stops and alerts on cookie timeout.
The proprietary internal mechanism handled automatically by the system. It sends a critical Slack alert requesting new cookies. The proprietary internal mechanism handled automatically by the system. The workflow will not resume until fresh cookies are supplied.
No — uses cookies only, never passwords.
No. RabbitAgent never logs in using a username or password. It only uses cookies, ensuring the system never processes sensitive data like credentials. This dramatically increases safety and avoids login-attempt detection by Facebook.
Verifies via DOM and fallback methods.
The proprietary internal mechanism handled automatically by the system. It checks response indicators and uses fallback methods if the DOM is slow. If no confirmation is detected, the job is marked as uncertain or failed.
Yes — uses ethical stealth mode.
Yes. The proprietary internal mechanism handled automatically by the system. This is done ethically and within Facebook’s guidelines, aiming to avoid false-positive flags without violating platform terms.
Yes — supports both posting modes.
Yes. The proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. This gives maximum flexibility for both personal and business publishing.
Inside the proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. This makes debugging easy and allows switching between accounts when needed.
Linear scaling — more instances = more capacity.
RabbitAgent scales linearly: each instance = one additional publishing pipeline. This means capacity can be increased simply by launching more agents on the same machine (up to RAM/CPU capacity) or across multiple servers. The system is practically infinitely scalable as long as the proprietary internal mechanism handled automatically by the system.
Only Playwright + lightweight libs.
The proprietary internal mechanism handled automatically by the system. No heavy dependencies are required. Playwright is installed once and rarely updated. The system is exceptionally easy to deploy on new machines.
Stop via SIGTERM, check Slack, restart.
Best practice is: (1) Stop the proprietary internal mechanism handled automatically by the system. (2) Wait for cleanup. (3) Check Slack for error messages. (4) Update cookies if needed. (5) Restart the proprietary internal mechanism handled automatically by the system. This prevents publishing from ending up in an inconsistent state.
No — proprietary internal mechanism handled automatically by the system.
No. The proprietary internal mechanism handled automatically by the system. It is 100% read-only regarding proprietary internal mechanism handled automatically by the system. Only the proprietary internal mechanism handled automatically by the system. This eliminates proprietary internal mechanism handled automatically by the system.
No — jobs are not duplicated.
No. proprietary internal mechanism handled automatically by the system. Once a job is marked 'done', the proprietary internal mechanism handled automatically by the system. The only exception is if an error results in an 'unverified publish', in which case the proprietary internal mechanism handled automatically by the system.
The operational module that posts on Facebook.
RabbitAgent is the operational publishing module in GoRabbit. It uses Playwright, cookies, and human-like behavior to publish safely and reliably in Facebook groups. The proprietary internal mechanism handled automatically by the system.
GoRabbit’s operational robot.
RabbitAgent is the operational component of GoRabbit that performs all actions on Facebook. While the proprietary internal mechanism handled automatically by the system. It mimics human behavior and is one of the core pillars of platform stability.
Executes all Facebook actions.
RabbitAgent executes all physical actions on Facebook on behalf of the proprietary internal mechanism handled automatically by the system. It reads proprietary internal mechanism handled automatically by the system. Without the proprietary internal mechanism handled automatically by the system.
Built on Playwright + modular design.
The proprietary internal mechanism handled automatically by the system. The architecture is modular and highly robust.
Runs on all GoRabbit servers.
RabbitAgent may run on proprietary internal mechanism handled automatically by the system.json. This provides flexibility, redundancy and strong operational reliability.
Contains session tokens. Critical proprietary internal mechanism handled automatically by the system.
tokens.json contains Facebook session cookies and Page Tokens. This is the credential set enabling the proprietary internal mechanism handled automatically by the system. Without valid tokens, nothing works. The proprietary internal mechanism handled automatically by the system.
Uses session cookies. Logs in when needed.
The proprietary internal mechanism handled automatically by the system.json. If they are expired, the proprietary internal mechanism handled automatically by the system. New cookies are generated and stored automatically. Slack is notified of all changes.
Reads queues + tokens + config.
RabbitAgent reads campaign_queue.json, warmup_queue.json, tokens.json, agent_config.json, gruppe_mapping.json and temporary status files. This makes the proprietary internal mechanism handled automatically by the system.
Status files, screenshots and Slack logs.
The proprietary internal mechanism handled automatically by the system. Everything is fully traceable.
Full set of Facebook actions.
The proprietary internal mechanism handled automatically by the system. All actions mimic human behavior.
Randomized actions create natural behavior.
The proprietary internal mechanism handled automatically by the system. This is one of the core mechanisms that keeps GoRabbit safe.
All proprietary internal mechanism handled automatically by the system.
agent_config.json defines the operational behavior: speed, timeout limits, retry counts, scroll intensity, render delays, max DOM depth, fallback strategy, screenshot levels and logging mode.
Detects risk and stops safely.
The proprietary internal mechanism handled automatically by the system. When risk is detected, publishing is halted and the proprietary internal mechanism handled automatically by the system.
Progressive retry logic.
If an action fails, the proprietary internal mechanism handled automatically by the system. If this fails again, the delay increases (progressive retries). After three failures, the group is flagged as problematic and the proprietary internal mechanism handled automatically by the system.
Linear scaling with multiple agents.
As many as needed. The system scales linearly. With 10 agents you publish ten times faster. The proprietary internal mechanism handled automatically by the system.
Publisher decides. proprietary internal mechanism handled automatically by the system.
The Publisher controls the proprietary internal mechanism handled automatically by the system. RabbitAgent does it. Publisher = the manager. proprietary internal mechanism handled automatically by the system. Both must function perfectly to maintain production stability.
Supports both headless and GUI.
RabbitAgent can run both headless and with a GUI. In production, headless mode is preferred for speed and stability, while in debugging mode GUI can be enabled to visually observe all steps — useful for troubleshooting or Facebook UI changes.
Uses heuristics and relative patterns.
The DOM parser uses visibility checks, relative positions, text anchors, aria-labels and heuristics to identify correct elements. Since Facebook frequently changes IDs and class names, logic is pattern-based rather than relying on fixed selectors.
Natural pauses that improve stability.
Micro-delays of 50–200 ms simulate natural human clicking behavior and prevent Facebook from perceiving automation. They also increase stability by giving elements time to respond before the next action.
Always a tested version in production.
RabbitAgent is tested and validated with newer Playwright versions. Upgrades are applied in a controlled manner only after UI tests in staging. This ensures stable production without unexpected compatibility issues.
Full multi-user support.
Yes. Each user has their own tokens.json and proprietary internal mechanism handled automatically by the system. A single server can run multiple independent agents, each working with its own account. The proprietary internal mechanism handled automatically by the system.
Variation + adaptive pauses.
The proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. Combined, this makes Facebook unlikely to detect automation.
Extra safe mode for new accounts.
Stealth Mode activates additional random patterns, wider variation in scrolling, human-like mouse movement simulation and more conservative posting timings. It is used when risk is detected or when the account is new.
Detailed logs + Slack.
The proprietary internal mechanism handled automatically by the system. Everything is sent to Slack and written locally.
Retry, fallback or stop.
Errors result in one of three actions: (1) retry with a short delay, (2) fallback posting, (3) full stop on high risk. The proprietary internal mechanism handled automatically by the system.
On errors, risk, or post completion.
Screenshots are captured when a post completes, upon validation failure, on risk detection, during DOM anomalies and whenever requested in debug mode. Images are stored temporarily for traceability.
8–15 seconds per action.
Speed ranges from 8–15 seconds per action depending on DOM complexity, group content and risk level. Higher risk results in slower and more conservative behavior.
Checks access and permissions.
The proprietary internal mechanism handled automatically by the system. Invalid groups are excluded automatically.
Highly stable and reliable.
RabbitAgent is designed for continuous operation and can handle hundreds of posts per session. It is resilient to temporary UI errors, network fluctuations and loading-time issues. Higher-risk situations are detected early.
15–35% CPU during activity.
RabbitAgent typically consumes 15–35% CPU during posting depending on the machine and browser proprietary internal mechanism handled automatically by the system. Headless mode is more resource-efficient than GUI mode.
300–900 MB per proprietary internal mechanism handled automatically by the system.
Memory usage typically ranges between 300–900 MB per proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
Resilient against unstable networks.
RabbitAgent handles temporary network drops, high latency and timeouts using retry and adaptive pauses. For prolonged issues, cooldown mode is activated and Slack is notified. Stability is prioritized over speed.
Reloads on DOM errors or freezes.
Facebook may freeze, stop loading or fail to display the input field. RabbitAgent reloads group pages when the DOM does not behave as expected. This dramatically increases stability during large campaigns.
Yes — and posting stops immediately.
Yes. The proprietary internal mechanism handled automatically by the system. When detected, publishing stops and the proprietary internal mechanism handled automatically by the system.
Safe mode with reduced speed.
Cooldown Mode activates when risk is detected or the account approaches rate limiting. The proprietary internal mechanism handled automatically by the system.
Designed for continuous operation.
Yes. The proprietary internal mechanism handled automatically by the system. With automatic memory cleanup, session refreshing, error handling and adaptive pacing, it can run for days at a time. A restart is recommended after large campaigns for clean resources.
Strict proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. tokens.json is treated as sensitive material and must never be stored in a repository.
Fallback to GUI on headless issues.
If headless mode fails, the proprietary internal mechanism handled automatically by the system. After the issue is resolved, the proprietary internal mechanism handled automatically by the system.
Fallback on UI changes.
When Facebook changes UI, DOM or button placement, the proprietary internal mechanism handled automatically by the system. It switches to fallback navigation and logs patterns to Slack. Developers can then hotfix selectors.
Unique machine_id per proprietary internal mechanism handled automatically by the system.
Each proprietary internal mechanism handled automatically by the system.json and its own output folders. When the proprietary internal mechanism handled automatically by the system.
Only temporary working files.
The proprietary internal mechanism handled automatically by the system. Nothing permanent is stored, and all content may be wiped after a campaign to minimize proprietary internal mechanism handled automatically by the system.
Clean shutdown with Slack notice.
The proprietary internal mechanism handled automatically by the system. It is then ready for a new session.
proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. Without the proprietary internal mechanism handled automatically by the system.
Facebook limits — not the proprietary internal mechanism handled automatically by the system.
The limitations are Facebook’s: rate limiting, risk on new accounts, blocked groups and temporary feature issues. RabbitAgent is not the limiting factor — Facebook is. The proprietary internal mechanism handled automatically by the system.
Full real-time status in Studio.
GoRabbit Studio displays the proprietary internal mechanism handled automatically by the system. All information updates in real time.
Semver-based versioning.
RabbitAgent uses a semver-inspired versioning scheme: major.minor.build. This allows the proprietary internal mechanism handled automatically by the system.
Heartbeat + Slack + proprietary internal mechanism handled automatically by the system.
RabbitAgent is monitored through Slack logs, internal heartbeat files, status directories and optionally proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system.
Automatic failover between Agents.
Yes. If one proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. This ensures high operational robustness.
The proprietary internal mechanism handled automatically by the system.
RabbitAgent is GoRabbit’s robot that performs all Facebook actions with human-like behavior, intelligent risk detection, robust DOM navigation and full integration with the proprietary internal mechanism handled automatically by the system.